CVE-2024-54380
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 Filippo Bodei WP Cookies Enabler wp-cookies-enabler allows PHP Local File Inclusion.This issue affects WP Cookies Enabler: from n/a through <= 1.0.1.
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 confidencePath Traversal vulnerability in the WP Cookies Enabler WordPress plugin allows unauthenticated attackers to perform Local File Inclusion (LFI) attacks by manipulating file path parameters with directory traversal sequences (e.g., ../../../). This can lead to disclosure of sensitive configuration files, source code, or other system files, potentially enabling further compromise.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Cookies Enabler plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Cookies Enabler' or check the /wp-content/plugins/ directory for a folder named 'cookies-enabler' or similar.Affected if The plugin is installed and active on the WordPress site.
-
Determine the installed plugin versionCheck the plugin header in its main PHP file (usually in wp-content/plugins/cookies-enabler/) for the 'Version' field, or view the plugin details in the WordPress Plugins page.Affected if The installed version has not been patched to address the path traversal vulnerability.
-
Identify accessible file-related parametersReview the plugin's PHP files for functions that handle file paths, particularly any that accept user input (via $_GET, $_POST, or $_REQUEST) and use it in file operations like include, require, fopen, or file_get_contents.Affected if The plugin contains file-handling code that processes user-supplied paths without proper sanitization.
-
Examine web server access logs for traversal attemptsSearch server access logs (Apache error.log, Nginx access.log) for requests containing patterns like '../', '..%2F', or '..\' in query parameters targeting the plugin.
A site is affected if WP Cookies Enabler plugin is installed and its version is older than the patched version that addresses the path traversal vulnerability allowing unauthenticated LFI attacks.
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.
From vendor dataUpgrade WP Cookies Enabler to the latest patched version. If no patch is available, disable the plugin. Additionally, implement WAF rules or web server configuration to block directory traversal patterns in request parameters.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54380 — 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-54380 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