CVE-2026-111574 Redirection for Contact Form 7 CVE debrief

Who should care

Defenders responsible for WordPress installations with the Redirection for Contact Form 7 plugin should assess exposure and prioritize updating to version 3.2.12 or later. This includes operators, platform administrators, vulnerability management teams, and security teams who manage WordPress deployments.

Why it matters

Defenders should prioritize verifying and updating the Redirection for Contact Form 7 plugin to prevent unauthenticated stored XSS attacks.

• Unauthenticated attackers can store malicious scripts in lead entries
• Logged-in users may execute malicious scripts when viewing lead entries in debug mode
• Verify plugin version and update to 3.2.12 or later to prevent exploitation
• Review lead entries for potential malicious scripts to prevent compromise

Technical summary

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. This vulnerability affects WordPress installations with the Redirection for Contact Form 7 plugin, particularly versions 2.2.7 to 3.2.11, and may allow unauthenticated stored XSS attacks.

Defensive priority

Defenders should prioritize verifying and updating the Redirection for Contact Form 7 plugin to version 3.2.12 or later, and review lead entries for potential malicious scripts.

Recommended defensive actions

• Verify and update the Redirection for Contact Form 7 plugin to version 3.2.12 or later
• Review lead entries for potential malicious scripts
• Enable debug mode only when necessary and monitor for suspicious activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on potential exploitation or affected versions beyond 2.2.7 to 3.2.11. Defenders should verify plugin version and review lead entries for potential malicious scripts. Limited evidence suggests unauthenticated attackers can store malicious scripts, which may execute when logged-in users view lead entries in debug mode. To verify, defenders should check plugin versions, review lead entries, and monitor for suspicious activity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.