# CVE-2026-111574: Redirection for Contact Form 7 2.2.7 - 3.2.11 - Unauthenticated Stored XSS via Lead Debug Metabox


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-fm6v-w7hr-3xm4

## What is CVE-2026-111574?

CVE-2026-111574 is a high-severity vulnerability in Unknown Redirection for Contact Form 7, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-111574?


## How do I fix CVE-2026-111574?

No fix has been published for CVE-2026-111574 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111574 being exploited?

There is no known exploitation of CVE-2026-111574 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111574 and fix it if it is affected.

What it is: CVE-2026-111574 is a high-severity vulnerability in Unknown Redirection for Contact Form 7, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111574 in the wild and no public exploit code.

Affected product: Unknown Redirection for Contact Form 7. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111574/ (Markdown: https://insights.sbomify.com/CVE-2026-111574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111574
- OSV: https://osv.dev/vulnerability/CVE-2026-111574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111574/
Summaries are generated and may contain mistakes; the official description above is the record.