UbermenuWordPress extension · Sevenspark
CVE-2024-3593
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 · uneditedThe UberMenu plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.8.3. This is due to missing or incorrect nonce validation on the ubermenu_delete_all_item_settings and ubermenu_reset_settings functions. This makes it possible for unauthenticated attackers to delete and reset the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe UberMenu WordPress plugin versions up to 3.8.3 lack proper nonce validation on the ubermenu_delete_all_item_settings and ubermenu_reset_settings functions. This CSRF vulnerability allows unauthenticated attackers to forge administrative requests that delete or reset plugin settings by tricking site administrators into clicking malicious links.
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
UbermenuWordPress extension
< 3.8.4CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify UberMenu plugin is installedCheck the WordPress plugins directory or navigate to Plugins > Installed Plugins in the WordPress admin dashboard to confirm the UberMenu plugin is presentAffected if UberMenu plugin is not installed on the WordPress site
-
Determine installed UberMenu versionIn WordPress admin, go to UberMenu > Settings (or similar) and locate the version number displayed, or check the plugin header in wp-content/plugins/ubermenu/ubermenu.php for the Version: fieldAffected if The installed version is lower than 3.8.4 (versions 3.x up to and including 3.8.3 are affected)
-
Confirm admin access to vulnerable functionsInspect the plugin files ubermenu_delete_all_item_settings and ubermenu_reset_settings functions in the plugin source code to verify they exist without nonce validationAffected if These functions exist without proper nonce validation checks (look for missing wp_verify_nonce or check_admin_referer calls)
-
Check if site admin may have clicked malicious linksReview server access logs for suspicious requests to admin-ajax.php or admin-post.php with action parameters related to ubermenu_delete_all_item_settings or ubermenu_reset_settingsAffected if Unusual or unexpected requests to these endpoints appear in logs without prior legitimate admin session
The site is affected if UberMenu plugin version is below 3.8.4 AND the vulnerable unauthenticated CSRF functions are present in the installation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.8.4
Update to a patched version of UberMenu when available. Until then, educate administrators about not clicking untrusted links, and consider implementing additional server-side CSRF protections.
3.8.4
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate the UberMenu plugin in the list
- Click the 'Update now' link if an update is available, or manually upload version 3.8.4 or higher of the UberMenu plugin
- Verify the plugin updated successfully to version 3.8.4 or later
- Test that the plugin functionality is working as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ubermenu
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3593 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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