dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-54310

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Aslam Khan Gouran Gou Manage My Account Menu gou-wc-account-tabs allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Gou Manage My Account Menu: from n/a through <= 1.0.1.8.

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

Missing Authorization vulnerability in the Gou Manage My Account Menu WordPress plugin (gou-wc-account-tabs). The plugin fails to properly enforce access control lists, allowing users to access functionality they should not be permitted to use. This is a classic Insecure Direct Object Reference (IDOR) or broken access control issue where authorization checks are missing or improperly implemented.

MitigationImplement proper role-based access control (RBAC) checks before executing any privileged functionality. Verify user permissions for each sensitive operation and ensure the plugin restricts menu and account tab access based on user roles. Update to the latest patched version when available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify if the Gou Manage My Account Menu plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'gou-wc-account-tabs' or search for 'Gou Manage My Account Menu' in the WordPress admin Plugins page
    Affected if The plugin folder 'gou-wc-account-tabs' exists in the plugins directory or the plugin appears in the WordPress admin plugin list
  2. Determine the installed plugin version
    Access the main plugin file (usually gou-wc-account-tabs.php) in the plugin folder and locate the version comment or header (e.g., 'Version: x.x.x')
    Affected if The plugin version cannot be determined or is earlier than the patched version (compare against any official security advisory once available)
  3. Inspect plugin menu and tab functionality
    Review the plugin source code for functions handling account menu tabs and user-specific data access. Look for PHP files in the plugin folder that handle 'my-account', 'menu', or 'tabs' functionality
    Affected if The plugin handles user account data without visible role or capability checks (functions execute without current_user_can() or similar authorization validation)
  4. Test for missing authorization on account endpoints
    Use a low-privilege user account (subscriber or customer role) to access the plugin menu and account tab features. Attempt to modify or view other users account data or access privileged functionality
    Affected if A user with limited role can access, modify, or view account information or menu options that should require higher privileges (e.g., administrator-only features)
  5. Verify access control implementation in plugin code
    Search plugin PHP files for authorization functions. Check if add_menu_page or related menu creation functions include proper capability checks (e.g., 'manage_options' capability)
    Affected if Menu items or account tab handlers lack capability checks or use overly permissive access rules (e.g., no check or 'read' capability for sensitive operations)

A user is affected if the Gou Manage My Account Menu plugin is installed and low-privilege users can access functionality or data that should require higher-level permissions due to missing authorization checks.

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

Implement proper role-based access control (RBAC) checks before executing any privileged functionality. Verify user permissions for each sensitive operation and ensure the plugin restricts menu and account tab access based on user roles. Update to the latest patched version when available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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