dbcve.org
Admin Menu EditorWordPress extension · W Shadow

CVE-2024-24876

HIGH · 8.8 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 1.12.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Janis Elsts Admin Menu Editor.This issue affects Admin Menu Editor: from n/a through 1.12.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Admin Menu Editor WordPress plugin. Attackers can trick authenticated administrators into unknowingly submitting malicious requests to modify menu configurations or perform administrative actions due to missing or inadequate anti-CSRF token validation on state-changing operations.

MitigationImplement WordPress nonces (wp_nonce_field/wp_verify_nonce) on all form submissions and AJAX actions that modify plugin settings or admin menu configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Admin Menu EditorWordPress extension
Affected:< 1.12.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Admin Menu Editor' (or 'W Shadow Admin Menu Editor'). The version number is displayed below the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/menu-editor/includes/files.php or similar main file.
    Affected if Installed version is lower than 1.12.1 (e.g., 1.12.0, 1.11.x, etc.)
  2. Locate plugin form handling code
    Access the plugin files via FTP or file manager. Navigate to the plugin directory (typically wp-content/plugins/menu-editor/). Search for PHP files that handle form submissions, particularly those that save or update menu configurations.
    Affected if No version is displayed or you cannot determine the version from plugin headers
  3. Verify nonce field implementation
    In the plugin's form handling files, search for 'wp_nonce_field' or '_wpnonce' to see if nonce fields are being generated in forms that modify menu settings. Look in files that handle state-changing operations like saving menus, adding items, or deleting items.
    Affected if Forms that modify menu configurations lack wp_nonce_field calls or nonce hidden input fields
  4. Verify nonce validation on form processing
    In the plugin's server-side form processing code, search for 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' to verify that submitted nonces are validated before processing state-changing requests.
    Affected if Form processing code does not call nonce verification functions before executing menu changes
  5. Check AJAX action handlers for nonce validation
    If the plugin uses AJAX to modify menus, examine its AJAX handlers (look for 'wp_ajax_' hooks). Verify that each handler calls wp_verify_nonce or check_ajax_referer before processing the request.
    Affected if AJAX endpoints that modify menu state do not validate nonces

You are affected if the installed Admin Menu Editor version is below 1.12.1 AND the plugin code lacks proper nonce validation (wp_nonce_field in forms and wp_verify_nonce in handlers) for state-changing operations.

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
Upgrade available Upgrade to 1.12.1 or later
Fixed in 1.12.1
Interim mitigation

Implement WordPress nonces (wp_nonce_field/wp_verify_nonce) on all form submissions and AJAX actions that modify plugin settings or admin menu configurations.

Recommended fix High confidence

1.12.1

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find 'Admin Menu Editor' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 1.12.1 from the WordPress plugin repository and upload it
  5. Verify the plugin version is showing 1.12.1 in the plugins list
  6. Test that the Admin Menu Editor functionality works correctly

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

Fix this in Admin Menu Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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