Skip to main content
Vulnerability Database/CVE-2026-111574

CVE-2026-111574: Contact Form 7 Redirection XSS Vulnerability

CVE-2026-111574 is a stored cross-site scripting vulnerability in the Redirection for Contact Form 7 WordPress plugin that lets attackers inject malicious scripts. This article covers the technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111574 Overview

CVE-2026-111574 is a stored Cross-Site Scripting (XSS) vulnerability in the Redirection for Contact Form 7 WordPress plugin before version 3.2.12. The plugin fails to sanitise or escape submitted form data stored as lead entries before rendering it in the lead debug metabox. Unauthenticated attackers can submit malicious JavaScript through a contact form that executes when a logged-in administrator views the lead entry with the plugin's debug mode enabled. The flaw is tracked under CWE-79 and affects the administrative interface of the WordPress site.

Critical Impact

Successful exploitation enables script execution in an authenticated administrator's browser session, potentially leading to full WordPress site takeover.

Affected Products

  • Redirection for Contact Form 7 WordPress plugin versions prior to 3.2.12
  • WordPress installations with the plugin's debug mode enabled
  • Administrator sessions viewing stored lead entries

Discovery Timeline

  • 2026-10-21 - CVE-2026-111574 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-111574

Vulnerability Analysis

The vulnerability is a stored XSS flaw in the lead-tracking functionality of the Redirection for Contact Form 7 plugin. When a visitor submits a Contact Form 7 form, the plugin stores the submitted data as a lead entry in the WordPress database. The plugin then renders this stored data inside a debug metabox on the administrative lead view screen without applying output encoding or input sanitisation.

An attacker submits form fields containing JavaScript payloads. The payload is persisted alongside legitimate lead data. When an administrator with debug mode enabled opens the entry, the browser parses the attacker-controlled markup and executes the embedded script in the administrator's authenticated context.

Exploitation requires user interaction from a privileged user and depends on the debug mode setting being enabled, which raises attack complexity. The impact extends to session hijacking, administrator account takeover, plugin or theme installation, and persistence through malicious users or scheduled tasks.

Root Cause

The root cause is missing output escaping in the lead debug metabox renderer. The plugin trusts stored form submission data and emits it directly into the admin page HTML. WordPress functions such as esc_html(), esc_attr(), or wp_kses_post() are not applied before output, allowing arbitrary HTML and script tags to render.

Attack Vector

The attack is network-based and unauthenticated at the submission stage. An attacker locates a public Contact Form 7 form on a target site running a vulnerable version of the plugin. The attacker submits a payload containing script content in one or more form fields. The payload lies dormant until an administrator views the lead entry with debug mode enabled, at which point the script executes in the admin browser.

See the WPScan Vulnerability Report F40440DE for additional technical details.

Detection Methods for CVE-2026-111574

Indicators of Compromise

  • Lead entries in the WordPress database containing HTML tags such as <script>, <img onerror=, or <svg onload= within form field values.
  • Unexpected administrator account creation or role elevation shortly after an administrator reviewed lead entries.
  • New plugin, theme, or wp-cron entries created during administrative sessions that opened lead debug views.

Detection Strategies

  • Query the wp_cf7_leads or related plugin tables for stored values containing angle brackets, javascript: URIs, or event handler attributes.
  • Review web server access logs for POST requests to Contact Form 7 endpoints with suspicious payloads in form parameters.
  • Monitor WordPress audit logs for administrative actions originating from the lead listing or debug metabox pages.

Monitoring Recommendations

  • Alert on administrator session activity that creates new users, modifies roles, or installs plugins immediately after accessing Contact Form 7 lead pages.
  • Enable Content Security Policy (CSP) reporting on the WordPress admin interface to surface inline script execution violations.
  • Track plugin version inventory across WordPress sites and flag instances of Redirection for Contact Form 7 below 3.2.12.

How to Mitigate CVE-2026-111574

Immediate Actions Required

  • Update the Redirection for Contact Form 7 plugin to version 3.2.12 or later across all WordPress sites.
  • Disable debug mode in the plugin configuration until the update is applied.
  • Audit existing lead entries for stored script payloads and purge entries containing untrusted HTML.
  • Rotate administrator credentials and invalidate active sessions if debug mode has been in use on vulnerable versions.

Patch Information

The vendor addressed the vulnerability in Redirection for Contact Form 7 version 3.2.12 by applying output escaping to lead data rendered in the debug metabox. Administrators should install the fix through the WordPress plugin updater or deploy it via managed WordPress tooling. Patch details are referenced in the WPScan Vulnerability Report F40440DE.

Workarounds

  • Turn off the plugin's debug mode so the vulnerable metabox does not render stored lead data.
  • Restrict administrator access to the lead management screens using role-based access controls until the patch is applied.
  • Deploy a web application firewall rule to block form submissions containing HTML tags or script indicators targeting Contact Form 7 endpoints.
bash
# Configuration example: update plugin via WP-CLI
wp plugin update wpcf7-redirect --version=3.2.12
wp plugin list --name=wpcf7-redirect --fields=name,status,version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.