CVE-2026-131793 in Contact Form To Any Api Plugin
Summary
by MITRE • 11/22/2026
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in IT Path Solutions Contact Form to Any API contact-form-to-any-api allows Stored XSS.This issue affects Contact Form to Any API: from n/a through 3.0.7.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/22/2026
The identified vulnerability represents a classic instance of Improper Neutralization of Input During Web Page Generation, commonly known as Cross-Site Scripting or XSS. Specifically, this flaw manifests within the IT Path Solutions Contact Form to Any API plugin for WordPress, affecting versions ranging from n/a through 3.0.7. The core technical deficiency lies in the application's failure to adequately sanitize and validate user-supplied input before it is processed by backend systems that subsequently render content back to users or store it in a database. In this specific context, the vulnerability allows for Stored XSS, which distinguishes it from reflected variants where malicious scripts are executed only during a single request session. Instead, stored vulnerabilities persist within the application's data storage layer, meaning that once an attacker successfully injects their payload, the malicious script is saved and will be delivered to every subsequent user who views the affected page or content area managed by this plugin.
From a technical perspective, the vulnerability likely stems from insufficient encoding of special characters such as angle brackets, quotes, and ampersands within form fields that are intended for public display or administrative review. When an attacker submits a crafted input containing JavaScript code via the contact form interface, the application accepts this data without applying appropriate output escaping mechanisms like HTML entity encoding or context-aware sanitization. Consequently, when the stored payload is later retrieved from the database and rendered in a web browser, it executes as native script rather than being treated as inert text. This behavior violates fundamental security principles regarding input validation and output encoding, which are critical for maintaining the integrity of client-side execution environments. The presence of this flaw indicates that the plugin does not strictly enforce allow-lists on acceptable characters or fails to strip potentially executable code blocks before persistence.
The operational impact of a Stored XSS vulnerability is severe because it transforms every visitor into an unwitting participant in the attack chain. Unlike reflected XSS, which requires social engineering tactics such as phishing links to trigger execution, stored XSS automatically executes upon page load for any user with access rights or public visibility depending on where the data is displayed. Attackers can leverage this capability to steal session cookies, hijack administrative sessions, perform actions on behalf of legitimate users without their knowledge, deface websites, or redirect traffic to malicious sites designed for further exploitation such as credential harvesting or malware distribution. In enterprise environments using WordPress plugins like Contact Form to Any API, the compromise of even a single user account with elevated privileges can lead to full site takeover, data exfiltration from connected APIs, and significant reputational damage due to compromised trust in the platform's security posture.
This vulnerability aligns directly with CWE-79, which categorizes Improper Neutralization of Input During Web Page Generation as Cross-site Scripting. Furthermore, within the MITRE ATT&CK framework for enterprise environments, this flaw facilitates techniques associated with Collection and Credential Access, specifically under T1056.004 (Input Capture: Web Portals) or potentially T1078 (Valid Accounts) if session hijacking is achieved through cookie theft. The persistence of the payload also relates to long-term access strategies where attackers maintain footholds by ensuring their malicious scripts remain active across multiple user sessions until remediation occurs.
To mitigate this vulnerability, immediate action must be taken by upgrading the Contact Form to Any API plugin to version 3.0.8 or later, which presumably includes patches for input sanitization and output encoding issues. For organizations unable to upgrade immediately due to compatibility constraints, implementing a Web Application Firewall (WAF) with rulesets tuned to detect and block XSS payloads in POST requests targeting contact forms can provide an effective compensating control. Additionally, developers should enforce strict Content Security Policy headers that restrict the execution of inline scripts, thereby neutralizing many stored XSS attacks even if they are successfully injected into the database. Regular security audits focusing on input validation logic across all user-facing endpoints and integrating static application security testing tools into the development lifecycle will help prevent similar flaws from being introduced in future updates.