# CVE-2026-121873: Redirection for Contact Form 7 2.6.0 - 3.2.15 - Unauthenticated Forged Personal Data Request Creation

> Unauthenticated visitors can create verified personal data erasure or export requests for addresses they do not control on WordPress sites using this plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-55f3-fr67-q9hv

## What is CVE-2026-121873?

CVE-2026-121873 is a medium-severity missing authorization vulnerability in Unknown Redirection for Contact Form 7, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Redirection for Contact Form 7 WordPress plugin before 3.2.16 does not verify ownership of the email address supplied through its data request form action and by default records the resulting request as already confirmed, allowing unauthenticated visitors to create verified WordPress personal data erasure or export requests for addresses they do not control.

Weakness: CWE-284 (Improper Access Control)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-121873 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121873 is a medium-severity missing authorization vulnerability in Unknown Redirection for Contact Form 7, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-121873 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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-121873/ (Markdown: https://insights.sbomify.com/CVE-2026-121873/index.md)
```

## Sources

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

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