Stored XSS in Contact Form by Supsystic
The Contact Form by Supsystic WordPress plugin is vulnerable to unauthenticated Stored Cross-Site Scripting due to insufficient sanitization of X-Forwarded-For headers.
CVE search metadata
CVE search record: CVE-2026-83625. Severity: high. CVSS: 7.2. KEV: no. Product: Contact Form by Supsystic (<= 1.10.2). Brief: Stored XSS in Contact Form by Supsystic. Brief link: https://feed.craftedsignal.io/briefs/2026-09-cve-2026-83625/
The Contact Form by Supsystic plugin for WordPress (versions 1.10.2 and earlier) contains a critical security flaw allowing for Stored Cross-Site Scripting (XSS). An unauthenticated attacker can exploit this vulnerability by manipulating HTTP headers, specifically the 'X-Forwarded-For' header, during the contact form submission process. Because the plugin fails to properly sanitize this input before storing and rendering it, injected JavaScript is executed within the browser of any user - including administrators - who views the malicious data in the WordPress dashboard or public-facing pages.
The vulnerability is compounded by a secondary issue involving the 'updateNonce' action, which lacks proper authentication checks. Attackers can leverage this to acquire a valid nonce, subsequently bypassing form protections to finalize the submission of the malicious XSS payload. Successful exploitation allows for account takeover, unauthorized administrative actions, or credential theft, depending on the privileges of the victim viewing the injected content.
Attack Chain
- Attacker sends an unauthenticated HTTP GET/POST request to the target site to trigger the 'updateNonce' action.
- The vulnerable plugin returns a valid nonce due to the absence of authentication checks on the 'updateNonce' endpoint.
- Attacker crafts a malicious HTTP request containing a scripted payload (e.g.,
<script>alert(1)</script>) inside the 'X-Forwarded-For' header. - The request is submitted to the plugin's contact form endpoint, including the previously obtained nonce.
- The plugin saves the form data, including the malicious script from the header, into the WordPress database without sanitization.
- A victim (likely an administrator) accesses the WordPress dashboard or a page displaying the form submissions.
- The browser renders the stored payload, executing the JavaScript in the context of the victim's session.
- The script performs unauthorized actions or exfiltrates session data to the attacker-controlled endpoint.
Impact
Successful exploitation of this vulnerability enables unauthenticated attackers to execute arbitrary JavaScript in the browsers of users viewing the injected content. This poses a high risk to WordPress site administrators, as it can lead to full site compromise, unauthorized configuration changes, or the theft of administrative session cookies.
Recommendation
- Update the Contact Form by Supsystic plugin to a version patched against CVE-2026-83625 immediately.
- Implement Web Application Firewall (WAF) rules to inspect and sanitize 'X-Forwarded-For' headers for script tags and malicious characters.
- Audit WordPress administrative logs for suspicious requests to the 'updateNonce' action.
- Review all stored contact form submissions for signs of anomalous script injection if administrative access was potentially compromised.
Immediate actions
Upgrade Contact Form by Supsystic to the latest patched version
Mitigations
Implement WAF blocking for script payloads in X-Forwarded-For headers
CVE-2026-83625
Detection coverage 1
Detect CVE-2026-83625 Exploitation - Malicious X-Forwarded-For Header
highDetects exploitation attempts targeting Contact Form by Supsystic by identifying script injection patterns in X-Forwarded-For headers
Detection queries are available on the platform. Get full rules →