dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-3238

HIGH · 8.8 CVSS v3.1 Published 2024-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The WordPress Menu Plugin — Superfly Responsive Menu plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.0.29. This is due to missing or incorrect nonce validation on the ajax_handle_delete_icons() function. This makes it possible for unauthenticated attackers to delete arbitrary files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Please not the CSRF was patched in 5.0.28, however, adequate directory traversal protection wasn't introduced until 5.0.30.

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 WordPress Superfly Responsive Menu plugin is vulnerable to CSRF in versions up to 5.0.29 due to missing nonce validation on the ajax_handle_delete_icons() function, allowing unauthenticated attackers to delete arbitrary files by tricking administrators into clicking malicious links. Although CSRF was patched in 5.0.28, directory traversal protection was only added in version 5.0.30.

MitigationUpdate the Superfly Responsive Menu plugin to version 5.0.30 or later to address both the CSRF and directory traversal vulnerabilities. Consider reviewing file deletion logs for suspicious activity.

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
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. Confirm Superfly Responsive Menu plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Superfly Responsive Menu' in the list of active plugins.
    Affected if The plugin is present in the WordPress installation
  2. Identify installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find the Superfly Responsive Menu entry and note the version number displayed below the plugin name.
    Affected if Version is 5.0.29 or earlier (any version up to and including 5.0.29)
  3. Check for vulnerable function in plugin files
    Access the WordPress site via file system or FTP. Navigate to wp-content/plugins/superfly-menu and locate the file containing ajax_handle_delete_icons(). This is typically in an includes or functions PHP file. Verify the function exists and lacks proper nonce validation.
    Affected if The ajax_handle_delete_icons() function exists and does not validate nonces before performing file operations
  4. Verify directory traversal protection is absent
    Examine the ajax_handle_delete_icons() function code to confirm whether it sanitizes file paths to prevent directory traversal (e.g., checks for '../' or uses realpath() validation).
    Affected if No path validation is present, allowing arbitrary file paths to be passed to the delete operation

User is affected if the Superfly Responsive Menu plugin is installed and the installed version is 5.0.29 or earlier, or if the ajax_handle_delete_icons() function lacks nonce validation and path sanitization regardless of version.

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 Superfly Responsive Menu plugin to version 5.0.30 or later to address both the CSRF and directory traversal vulnerabilities. Consider reviewing file deletion logs for suspicious activity.

Recommended fix High confidence

Version 5.0.30 or later of the Superfly Responsive Menu plugin

  1. Backup your WordPress site before making any changes
  2. Update the Superfly Responsive Menu plugin to version 5.0.30 or later through the WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository)
  3. Verify the plugin update was successfully applied by checking the plugins page
  4. Confirm the installed version shows 5.0.30 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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 locally
dbcve dependency scanner

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