Stored XSS in Contact Form 7 Redirection Plugin Debug Output

The Redirection for Contact Form 7 WordPress plugin before 3.2.12 does not sanitise or escape submitted form data stored as lead entries before outputting it in the lead debug metabox, allowing unauthenticated attackers to store a malicious script that executes when a logged-in user views the entry with the Redirection for Contact Form 7 WordPress plugin before 3.2.12's debug mode enabled.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

This vulnerability is a stored cross-site scripting (XSS) flaw in the Redirection for Contact Form 7 WordPress plugin that allows unauthenticated attackers to inject malicious scripts through form submissions. The vulnerability exists because user-submitted form data is not properly sanitized or escaped before being displayed in the plugin's debug metabox, a feature typically accessed by logged-in administrators. When an admin views a form entry with debug mode enabled, the stored malicious script executes in their browser with their privileges, potentially leading to account compromise, data theft, or further site exploitation. This affects WordPress sites using versions of the plugin before 3.2.12, making it a critical risk for any organization relying on Contact Form 7 for lead collection and management.

Casky's 323 matching skills detect this attack pattern by mapping it to MITRE techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Claude AI with extended reasoning identifies the attack chain: first, the reconnaissance phase where attackers probe for the vulnerable plugin, followed by initial access through form submission with XSS payloads. Practitioners using Casky would see findings flagging unsanitized user input flowing into administrative interfaces, improper output encoding in debug functions, and the absence of Content Security Policy headers that could mitigate XSS execution. The platform would highlight the critical gap between input validation (missing) and output encoding (missing), correlating this with the CWE-79 classification and recommending immediate plugin updates, input validation implementation, and security headers as remediation steps.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-111574.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-111574

Casky has 323 skills that investigate the attack patterns behind CVE-2026-111574. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn