dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-7894

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-07
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
The If Menu plugin for WordPress is vulnerable to unauthorized modification of the plugin's license key due to a missing capability check on the 'actions' function in versions up to, and including, 0.19.1. This makes it possible for unauthenticated attackers to modify delete or modify the license key.

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 If Menu WordPress plugin lacks a capability check on its 'actions' function, allowing unauthenticated attackers to modify or delete the plugin's license key. This is a broken access control vulnerability (CWE-862) where the plugin fails to verify user permissions before allowing sensitive configuration changes.

MitigationUpdate the plugin to version 0.19.2 or later which includes proper capability validation. Until then, consider disabling the plugin or restricting access to the admin area via firewall rules.

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 Menu plugin installation and version
    Log into WordPress admin, go to Plugins > Installed Plugins, locate 'If Menu' (or 'If Menu - Visibility Rules for Menu Items') and note the version number displayed
    Affected if The plugin is installed and the version shown is lower than 0.19.2 (e.g., 0.19.1, 0.19.0, etc.)
  2. Verify version via plugin files
    Access the plugin directory via FTP or file manager, open the main plugin file (if-menu.php) and locate the 'Version' header comment
    Affected if The version header shows a number less than 0.19.2
  3. Confirm the vulnerable actions function exists
    Inspect the plugin source code in the admin menu or settings handler file, look for any function handling 'actions' or license key operations that lacks a current_user_can() capability check
    Affected if The code shows an actions handler (e.g., save_license, delete_license, or similar) without a current_user_can() verification at the function entry point
  4. Test unauthenticated access to license settings
    Using a tool like curl, send a POST request to the WordPress admin-ajax.php endpoint with the 'action' parameter set to the plugin's action (e.g., if_menu_save_license) without providing authentication cookies
    Affected if The request returns a successful response (HTTP 200) rather than a 401/403 error, indicating the function is accessible without authentication

You are affected if the If Menu plugin is installed with any version prior to 0.19.2 and the plugin's license key settings can be modified without authentication.

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 the plugin to version 0.19.2 or later which includes proper capability validation. Until then, consider disabling the plugin or restricting access to the admin area via firewall rules.

Recommended fix Moderate confidence

Latest version (greater than 0.19.1)

  1. Log in to the WordPress admin dashboard.
  2. Navigate to Plugins > Installed Plugins.
  3. Locate the 'If Menu' plugin in the list.
  4. Click 'Update Now' if an update is available, or ensure you are running the latest version of the plugin.
  5. Verify that the installed version is greater than 0.19.1.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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