dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-54323

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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 Saad Iqbal New User Approve new-user-approve allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects New User Approve: from n/a through <= 2.6.2.

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

This is a Missing Authorization vulnerability in the WordPress 'New User Approve' plugin (versions <= 2.6.2). The plugin fails to properly enforce access control checks, allowing attackers to exploit incorrectly configured security levels and potentially perform actions reserved for higher-privileged users.

MitigationUpdate the New User Approve plugin to the latest version which should include proper role-based access control (RBAC) checks. If no update is available, manually audit the plugin code to add authorization checks before sensitive 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Verify New User Approve plugin is installed
    Navigate to WordPress admin Dashboard > Plugins > Installed Plugins. Locate 'New User Approve' in the list and confirm it is installed.
    Affected if The plugin is present in the WordPress installation
  2. Confirm the plugin is active
    In the Installed Plugins list, check if 'New User Approve' has the 'Active' status enabled.
    Affected if The plugin is currently active on the WordPress site
  3. Check installed plugin version
    In the Installed Plugins list, click on 'New User Approve' to view the plugin details, or look for the version number displayed under the plugin name in the list.
    Affected if The installed version is visible and can be compared against the affected range
  4. Compare version against affected range
    Take the version number found in the previous step and compare it to 2.6.2. Any version less than or equal to 2.6.2 falls within the affected range.
    Affected if The installed version is 2.6.2 or lower

A user is affected if the New User Approve plugin is active and the installed version is 2.6.2 or lower, as this version range lacks proper role-based access control enforcement.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the New User Approve plugin to the latest version which should include proper role-based access control (RBAC) checks. If no update is available, manually audit the plugin code to add authorization checks before sensitive operations.

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-2024-54323 — 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-2024-54323 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