dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-4314

HIGH · 8.8 CVSS v3.1 Published 2026-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The 'The Ultimate WordPress Toolkit – WP Extended' plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.2.4. This is due to the `isDashboardOrProfileRequest()` method in the Menu Editor module using an insecure `strpos()` check against `$_SERVER['REQUEST_URI']` to determine if a request targets the dashboard or profile page. The `grantVirtualCaps()` method, which is hooked into the `user_has_cap` filter, grants elevated capabilities including `manage_options` when this check returns true. This makes it possible for authenticated attackers, with Subscriber-level access and above, to gain administrative capabilities by appending a crafted query parameter to any admin URL, allowing them to update arbitrary WordPress options and ultimately create new Administrator accounts.

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 · high confidence

The WP Extended plugin for WordPress has a privilege escalation vulnerability in versions up to 3.2.4. The isDashboardOrProfileRequest() method uses an insecure strpos() check against $_SERVER['REQUEST_URI'] to determine if a request targets dashboard/profile pages. The grantVirtualCaps() method, hooked to user_has_cap filter, grants elevated capabilities including manage_options when this check returns true. Attackers with Subscriber-level access can append crafted query parameters to admin URLs to gain administrative capabilities.

MitigationUpgrade to version 3.2.5 or later. Until then, restrict Subscriber-level accounts or disable the plugin if possible.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP Extended plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin, or inspect /wp-content/plugins/ directory for wp-extended folder
    Affected if Plugin files exist in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, click on the WP Extended plugin to view details, or read the version header from the main plugin PHP file (e.g., wp-extended.php)
    Affected if Version is 3.2.4 or lower (versions 3.2.5 and later contain the fix)
  3. Verify plugin is active
    Check the Plugins page in WordPress admin - look for 'Active' status under WP Extended
    Affected if Plugin is currently active and version is 3.2.4 or lower
  4. Check for Subscriber-level user accounts
    Navigate to Users > All Users in WordPress admin; look for users with 'Subscriber' role, or query wp_users and wp_usermeta tables for subscriber role
    Affected if At least one Subscriber-level user exists in the system

A user is affected if WP Extended plugin version 3.2.4 or lower is active on the WordPress site and at least one Subscriber-level user account exists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 3.2.5 or later. Until then, restrict Subscriber-level accounts or disable the plugin if possible.

Recommended fix Moderate confidence

Latest version after 3.2.4 (check WordPress plugin repository for current stable release)

  1. 1. Update the 'The Ultimate WordPress Toolkit – WP Extended' plugin to the latest available version from the WordPress plugin repository.
  2. 2. After updating, verify that the privilege escalation vulnerability is resolved by testing that lower-privileged users (Subscriber level) cannot gain administrative capabilities.
  3. 3. Review user accounts to ensure no unauthorized Administrator accounts were created during the time the vulnerability was exploitable.
  4. 4. Consider resetting passwords for administrative accounts as a precautionary measure.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4314 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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