CVE-2023-23990
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper Privilege Management vulnerability in WordPress plugin Redirection for Contact Form 7 (wpcf7-redirect) allows authenticated users to escalate their privileges beyond what their role should permit. This affects versions through 2.7.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin installationAccess your WordPress site via FTP or file manager and navigate to /wp-content/plugins/ directory. Look for a folder named 'wpcf7-redirect' or 'redirection-for-contact-form-7'.Affected if The plugin folder exists in the plugins directory
-
Identify the installed versionOpen the main plugin file (usually wpcf7-redirect.php or similar) in the plugin folder and locate the version declaration in the plugin header comment, or check the readme.txt file for the 'Stable tag' entry.Affected if The version number listed is 2.7.0 or lower, or if no version is found but the plugin is present on a WordPress site through early 2023
-
Verify the plugin is activeLog into WordPress admin dashboard, go to Plugins > Installed Plugins, and check if 'Redirection for Contact Form 7' is activated.Affected if The plugin shows as active and the version cannot be determined or is 2.7.0 or lower
-
Check for existing user accountsIn WordPress admin, navigate to Users > All Users and review the list of registered users on the site.Affected if There are any registered users beyond a single administrator account (authenticated users exist)
-
Inspect user role capabilitiesUse a role editor plugin or query the wp_options table for the 'wp_user_roles' option to examine role definitions. Specifically look for whether lower-privileged roles (editor, author, contributor, subscriber) have administrative-level capabilities.Affected if Non-administrator roles unexpectedly possess capabilities typical of administrator roles (such as 'manage_options', 'edit_users', or 'delete_users')
Your environment is affected if the wpcf7-redirect plugin versions 2.7.0 or earlier are installed and active on a WordPress site that has multiple user accounts with role-based access controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to version 2.7.1 or later which contains the fix. If immediate update is not possible, restrict user permissions or disable the plugin until patching is feasible.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23990 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data