CVE-2026-23970: Unauthenticated XSS in Contact Form 7 ≤3.2.8 – Patch Now
Contact Form 7 version 3.2.8 and earlier contain an unauthenticated Cross-Site Scripting vulnerability in the form redirection functionality. An attacker can inject malicious JavaScript into a redirect parameter, and when a victim visits or completes the form, the script executes in their browser. This doesn't require the attacker to be authenticated or logged in, making it a low-friction attack vector.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.1 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
Unauthenticated Cross Site Scripting (XSS) in Redirection for Contact Form 7 <= 3.2.8 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-23970 is an unauthenticated reflected XSS vulnerability (CWE-79) in Contact Form 7's redirection handler. The vulnerability exists in form versions 3.2.8 and below. The attack vector is network-based, complexity is low, and the exploit requires user interaction—specifically, a victim must visit a crafted link or submit a form with attacker-controlled redirect parameters. The resulting script execution occurs in the victim's browser context with the same privileges as the user, enabling credential theft, session hijacking, or phishing payloads. The CVSS 3.1 score of 7.1 (HIGH) reflects a wide attack surface (unauthenticated), moderate impact (CIA all affected at low level), and cross-site request scope.
Business impact
Organizations running Contact Form 7 risk compromise of visitor and customer data entered through contact forms. XSS payloads can harvest email addresses, names, phone numbers, or other personal information submitted mid-form. Additionally, attackers can redirect users to phishing sites or malicious domains, damaging trust and brand reputation. Website administrators should prioritize patching to prevent data exfiltration and maintain compliance with privacy frameworks (GDPR, CCPA).
Affected systems
Contact Form 7 version 3.2.8 and all earlier versions are affected. The plugin is widely deployed on WordPress sites for contact form functionality. Organizations using version 3.2.9 or later are not affected. Verify your installed version in WordPress admin settings or through the plugin metadata.
Exploitability
This vulnerability has moderate exploitability. While it requires victim interaction—the victim must click a malicious link or the attacker must inject a payload into a form submission—the attack is unauthenticated and does not require special conditions. An attacker could craft a URL with a malicious redirect parameter and distribute it via email, social engineering, or compromised search results. No exploit code or proof-of-concept is required; standard JavaScript injection techniques apply. The CVSS vector reflects that remediation is not applied automatically, giving the vulnerability sufficient headroom for widespread abuse if left unpatched.
Remediation
Upgrade Contact Form 7 to version 3.2.9 or later. This patch corrects the unsafe redirection handling and sanitizes user-supplied redirect parameters. After updating, test contact form submissions and confirm that legitimate redirects still function. No database migration or configuration changes are required. Organizations unable to upgrade immediately should restrict access to contact forms or implement Web Application Firewall (WAF) rules to block requests containing suspicious redirect parameters.
Patch guidance
WordPress administrators should apply the security update to Contact Form 7 as soon as possible. The patch is available through the WordPress plugin directory. Navigate to Plugins > Installed Plugins, select Contact Form 7, and click Update if version 3.2.9 or later is available. Alternatively, download the patched version directly from the official Contact Form 7 WordPress repository and upload it manually if automatic updates are disabled. Verify the update completion by confirming the plugin version in the plugin list.
Detection guidance
Monitor web server and WAF logs for requests containing suspicious redirect parameters in Contact Form 7 submissions (e.g., URLs with 'redirect', 'url', or similar parameters containing JavaScript, data: URIs, or protocol handlers like 'javascript:'). Check for 400/403 responses if WAF rules block such requests. Use SIEM tools to correlate form submission logs with subsequent outbound requests to external domains, which may indicate successful exploitation. For WordPress sites, enable security logging plugins that track plugin version and update status to ensure timely patching. Scan user-submitted form data for encoded or obfuscated script tags.
Why prioritize this
This vulnerability merits high priority due to its combination of unauthenticated access, low attack complexity, and cross-site scope. Contact Form 7 is a ubiquitous WordPress plugin, making the affected user base large. The ability to execute arbitrary JavaScript in visitor browsers without authentication makes it attractive for opportunistic attackers. The HIGH CVSS score reflects legitimate confidentiality, integrity, and availability impact. Organizations should prioritize patching before attackers develop and distribute automated exploitation frameworks.
Risk score, explained
The CVSS 3.1 score of 7.1 (HIGH) is driven by several factors: (1) Network-based attack vector with no authentication required, (2) Low attack complexity—standard XSS injection, (3) Required user interaction—the victim must click a link or submit a form, (4) Changed scope—the vulnerability can affect confidentiality, integrity, and availability across the web application and user context, and (5) Low-to-moderate impact on all three security properties. The score reflects a threat that is achievable by moderately skilled attackers but not trivially exploitable without some social engineering or distribution effort.
Frequently asked questions
Does my site need to be actively promoting or linking to malicious forms for exploitation to occur?
No. An attacker can craft a direct URL with a malicious redirect parameter and send it via email, forums, or third-party sites. Any visitor who clicks the link or who is redirected via a compromised advertisement may be exploited. No prior relationship or promotion from your site is necessary.
Can Contact Form 7's built-in redirects be exploited, or only custom ones?
The vulnerability affects the redirection functionality of Contact Form 7 generally. If your forms are configured with any redirect option—custom or built-in—review your redirect URLs and ensure they do not accept user input. Update to version 3.2.9 or later to remove the vulnerability entirely.
If we update to version 3.2.9, will existing form submissions and settings be preserved?
Yes. The patch does not require migration or configuration changes. All form settings, submissions, and user data are preserved. After updating, test one or two forms to confirm they function as expected, particularly any that use custom redirects.
How can I check if my site has been compromised via this vulnerability?
Review your website logs for unusual redirect attempts in Contact Form 7 submissions. Check your user analytics for unexpected traffic spikes to external domains around form submission timestamps. Inspect form submissions in the Contact Form 7 database or logs for obfuscated JavaScript or suspicious URLs. If you suspect compromise, run a security scanner, review user account activity, and consider notifying visitors if personal data was submitted.
This intelligence is current as of the publication date and based on vendor advisories and CVE data available at that time. CVSS scores and severity ratings are subject to change. No exploit code is provided. Organizations should verify patch availability against the official Contact Form 7 WordPress plugin directory and vendor advisory before deploying. Testing in a non-production environment is recommended. This analysis is for informational purposes and does not constitute legal, regulatory, or professional security advice. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20066HIGHWordPress CP Polls 1.0.8 Persistent XSS Vulnerability
- CVE-2016-20084HIGHWordPress Appointment-Booking-Calendar Unauthenticated XSS and Privilege Escalation
- CVE-2023-33999HIGHDOM-Based XSS in WP Mail Log Plugin – Analysis & Remediation
- CVE-2023-54351HIGHStored XSS in WordPress Sonaar Music Plugin 4.7 – Patch & Detection Guide
- CVE-2025-11262HIGHLink Whisper Free Stored XSS Vulnerability – Analysis & Patch Guidance
- CVE-2025-14773HIGHABB T-MAC Plus XSS Vulnerability – HIGH Risk Assessment
- CVE-2025-15654HIGHFox-themes Prague Reflected XSS Vulnerability – CVSS 7.1 (HIGH)
- CVE-2025-52759HIGHReflected XSS in UnboundStudio Accordion FAQ Plugin (Versions ≤2.2.1)