dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-24364

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in weDevs WP User Frontend wp-user-frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through <= 4.2.5.

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 confidence

The WP User Frontend plugin for WordPress versions up to 4.2.5 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This means the plugin fails to properly verify user permissions before allowing access to certain functionality, potentially enabling authenticated users to perform actions beyond their intended privileges.

MitigationUpdate WP User Frontend to the latest version once available, and review all endpoints and functions in the plugin to ensure proper capability checks and authorization validations are enforced before executing privileged operations.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 User Frontend plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP User Frontend' in the list. Alternatively, check the /wp-content/plugins/ directory for the wp-user-frontend folder.
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins, find WP User Frontend, and note the version number displayed. Or inspect the main plugin file header in wp-content/plugins/wp-user-frontend/wpuf.php for the Version field.
    Affected if Version is 4.2.5 or lower (including any 4.x.x version up to 4.2.5)
  3. Check for improperly configured access control levels
    Review the plugin settings under WP User Frontend > Settings > General tab. Look for any access control, capability, or role settings that may be set to allow lower-privileged users (such as Subscribers or Contributors) to access administrative or privileged functionality.
    Affected if Any user role below Administrator has been granted access to privileged plugin features or endpoints
  4. Verify authorization on plugin endpoints
    If you have access to the site files, inspect the plugin code for functions that handle user actions (typically in includes/ or class files). Look for missing current_user_can() or wpuf_verify_nonce() calls before performing privileged operations.
    Affected if Plugin endpoints execute actions without proper capability or permission checks

A user is affected if WP User Frontend version 4.2.5 or lower is installed AND the plugin exposes privileged functionality to users without proper authorization verification.

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

Update WP User Frontend to the latest version once available, and review all endpoints and functions in the plugin to ensure proper capability checks and authorization validations are enforced before executing privileged operations.

Recommended fix Moderate confidence

Latest version of WP User Frontend (version > 4.2.5)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP User Frontend plugin
  4. Check if update is available and update to the latest version
  5. Verify the update was successful

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24364 — 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-24364 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