Mega MenuWordPress extension · Stylemixthemes
CVE-2024-35677
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in StylemixThemes MegaMenu allows PHP Local File Inclusion.This issue affects MegaMenu: from n/a through 2.3.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 · high confidenceA path traversal vulnerability in StylemixThemes MegaMenu plugin allows unauthenticated attackers to perform Local File Inclusion (LFI) by manipulating path parameters. The plugin fails to properly validate and restrict file paths, enabling attackers to read sensitive server files via directory traversal sequences (e.g., ../../../). This can lead to exposure of configuration files, credentials, and potentially remote code execution if certain files are included.
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
Mega MenuWordPress extension
< 2.3.13CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify MegaMenu plugin installation and versionAccess WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Mega Menu' by Stylemixthemes, and note the version number displayed. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/megamenu/) for the version comment or header.Affected if The installed version is below 2.3.13 (e.g., 2.3.12, 2.3.0, 1.x, etc.) or the version cannot be determined but the plugin is present.
-
Identify vulnerable plugin filesLocate the plugin's main PHP files, particularly any files handling menu rendering or path parameters. Common locations include wp-content/plugins/megamenu/megamenu.php or similar entry points. Search for functions that accept file path arguments (e.g., include, require, file_get_contents).Affected if The plugin code contains functions that accept user-controlled path parameters without sanitization.
-
Inspect web server access logs for traversal attemptsReview web server access logs (Apache error.log, Nginx access.log, or WP debug.log) for patterns containing '../', '..%2F', or URL-encoded traversal sequences targeting the MegaMenu plugin endpoints. Common attack patterns include requests to /?mm_path=../../../etc/passwd or similar.Affected if Logs contain directory traversal requests (e.g., ../, ..%2F) aimed at MegaMenu endpoints or parameters.
-
Check for recently modified or new suspicious filesList files in the wp-content/uploads/ directory and the plugin directory. Look for unexpected PHP files with random names, webshells, or files modified around the time of potential exploitation.Affected if Unexpected PHP files exist in upload directories or the plugin directory, suggesting successful LFI or RCE exploitation.
A user is affected if the Stylemixthemes Mega Menu plugin version is installed and is lower than 2.3.13, and the vulnerable path parameter functionality is accessible to unauthenticated users.
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 · scoped2.3.13
Update MegaMenu to the latest patched version when available. Implement web application firewall rules to block directory traversal patterns. If immediate update is not possible, disable the plugin until a patch is released.
Mega Menu version 2.3.13
- 1. Backup your WordPress site and database before proceeding with any updates.
- 2. Navigate to the WordPress admin dashboard.
- 3. Go to Plugins > Installed Plugins.
- 4. Find the 'Mega Menu' plugin by StylemixThemes.
- 5. If an update is available, click 'Update Now' to upgrade to version 2.3.13 or later.
- 6. Alternatively, download the latest version from the WordPress Plugin Repository or StylemixThemes website.
- 7. After updating, verify the plugin version shows 2.3.13 or higher.
- 8. Test the Mega Menu functionality to ensure it works correctly after the update.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mega Menu
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35677 — 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-35677 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