Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconIdentify WordPress site with vulnerable plugin
-
DeliveryCraft XSS payload in form field
-
ExploitSubmit unauthenticated contact form
-
InstallPlugin stores or reflects unsanitized input
-
C2Victim loads affected page
-
ExecuteMalicious script executes in victim browser
-
ImpactSession token or credential exfiltrated
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No authentication is required to submit input to the contact form (confirmed by PR:N in the CVSS vector). However, exploitation requires that a victim user (site visitor, editor, or administrator) subsequently loads a page rendering the malicious input, as indicated by UI:R in the CVSS vector. Limiting factors include: the target WordPress site must have the Contact Form by Supsystic plugin installed and active in a version prior to 1.10.0; a real user must interact with or navigate to the page containing the injected content before the script executes; and the attacker cannot directly control when or whether a victim will trigger the payload. The attack does not require any non-default configuration of the plugin - any site with a publicly accessible contact form is exposed. |
| Impact | The CVSS 7.1 score is driven by a favorable-to-attacker combination of network accessibility, low complexity, and no required privileges (AV:N/AC:L/PR:N), moderated by the need for victim interaction (UI:R) and relatively low individual impact metrics (C:L/I:L/A:L). No EPSS score, CISA KEV listing, or confirmed proof-of-concept code is referenced in the available intelligence, which collectively suggests this has not yet been observed in active, widespread exploitation campaigns. The A:L availability metric in the provided CVSS vector warrants scrutiny - traditional XSS does not directly impair service availability, and this metric may modestly inflate the composite score. That said, even a mid-sized municipal IT team in mielec running a public WordPress site with this plugin installed should treat the patch as near-term rather than deferrable, given the zero-privilege entry point and the real potential for session theft or phishing via script injection. The absence of KEV listing should not be read as safety: unauthenticated, network-reachable XSS in a publicly accessible contact form is a straightforward target for opportunistic attackers. |
| Exploit ScenarioDerived | An unauthenticated attacker visits a WordPress site running Contact Form by Supsystic before version 1.10.0 and submits a contact form containing a crafted XSS payload in one of the input fields. The plugin stores or reflects the unsanitized input, and when a site visitor or administrator subsequently loads the affected page, the malicious script executes in their browser, potentially exfiltrating session cookies or WordPress nonces to an attacker-controlled server. No proof-of-concept code has been identified at time of analysis, but the attack pattern is well-understood and trivially reproducible for any attacker familiar with WordPress plugin XSS techniques. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 18, 2026
Unauthenticated cross-site scripting in Contact Form by Supsystic WordPress plugin (all versions before 1.10.0) allows a remote, unauthenticated attacker to inject and execute arbitrary JavaScript in the browsers of site visitors. The CVSS vector confirms a scope change (S:C), meaning the injected script executes in the victim's browser context rather than the server, enabling session hijacking, credential theft, or malicious redirects. No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-privilege entry point and WordPress deployment scale make this a meaningful patching priority.
RemediationAI
Update Contact Form by Supsystic to version 1.10.0 or later immediately; this is the vendor-released patch as documented in the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/contact-form-by-supsystic/vulnerability/wordpress-contact-form-by-supsystic-plugin-1-10-0-cross-site-scripting-xss-vulnerability. If immediate patching is not possible, consider deploying a Web Application Firewall with XSS filtering rules targeting the plugin's form submission endpoints - note that overly aggressive WAF rules may block legitimate form submissions and should be tested in audit mode first. As a more disruptive but effective interim control, deactivating the plugin entirely on public-facing pages eliminates the attack surface at the cost of losing the contact form functionality. Administrators should also audit server and application logs for anomalous or encoded payloads in form submission fields, which may indicate prior exploitation attempts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected product is the Contact Form by Supsystic WordPress plugin, identified by CPE cpe:2.3:a:supsystic:contact_form_by_supsystic:*:*:*:*:*:*:*:*. CWE-79 (Improper Neutralization of Input During Web Page Generation) is the root cause class, indicating that user-supplied data submitted through the contact form is not properly sanitized or encoded before being rendered into HTML output. This classic XSS pattern in WordPress plugins typically manifests as either stored XSS (malicious input persisted to the database and served to all subsequent page viewers) or reflected XSS (malicious input echoed back in an HTTP response). The CVSS scope change (S:C) strongly suggests the impact crosses from the WordPress application context into the victim's browser environment, consistent with how XSS payload execution operates. The Patchstack advisory is the sole intelligence source, and the plugin's form-handling PHP code fails to apply sufficient output escaping.
Know when Contact Form By Supsystic gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Network-reachable, no privileges needed, scope changes to victim browser; availability impact dropped to N as XSS does not directly impair service.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
2DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in Contact Form by Supsystic < 1.10.0 versions.
Executive ViewAI
The Contact Form by Supsystic WordPress plugin creates an unauthenticated vulnerability on your website that could compromise visitor credentials and sessions, affecting customer trust and exposing sensitive data. All versions before 1.10.0 are vulnerable, and no vendor patch is currently available, requiring immediate compensating controls to protect your brand and customer data. This represents a HIGH-severity risk to any organization using this popular WordPress plugin.
No vendor-released patch identified at time of analysis. Interim mitigations include: deploying content security policy (CSP) headers to restrict inline script execution; configuring Web Application Firewall (WAF) rules to block script injection attempts; disabling the plugin on non-critical sites; implementing strict input validation and output encoding on contact form submissions; enabling security response headers (X-Frame-Options, X-Content-Type-Options, X-XSS-Protection); continuous monitoring for malicious activity targeting contact form endpoints; and evaluating alternative contact form plugins pending vendor patch release.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Contact Form By Supsystic
View allRemote code execution in Contact Form by Supsystic plugin for WordPress (all versions ≤1.7.36) allows unauthenticated at
Stored cross-site scripting in the Contact Form by Supsystic WordPress plugin (all versions ≤1.10.2) allows unauthentica
Unauthenticated authentication bypass in the Contact Form by Supsystic WordPress plugin (versions before 1.10.0) exposes
EUVD-2026-60793
GHSA-pr7v-7wv9-4xjq
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB