# CVE-2023-23990: WordPress Redirection for Contact Form 7 plugin <= 2.7.0 - Privilege Escalation vulnerability

> An attacker can escalate privileges in the Redirection for Contact Form 7 WordPress plugin due to improper privilege management.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 May 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-6w8m-grv3-w8wv

## What is CVE-2023-23990?

CVE-2023-23990 is a high-severity vulnerability in Qube One Ltd. Redirection for Contact Form 7, published on 17 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Improper Privilege Management vulnerability in Qube One Ltd. Redirection for Contact Form 7 wpcf7-redirect allows Privilege Escalation.This issue affects Redirection for Contact Form 7: from n/a through 2.7.0.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-23990?


## How do I fix CVE-2023-23990?

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

## Is CVE-2023-23990 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23990 and fix it if it is affected.

What it is: CVE-2023-23990 is a high-severity vulnerability in Qube One Ltd. Redirection for Contact Form 7, published on 17 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-23990 in the wild and no public exploit code.

Affected product: Qube One Ltd. 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-2023-23990/ (Markdown: https://insights.sbomify.com/CVE-2023-23990/index.md)
```

## Sources

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

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