CVE-2024-4347
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 WP Fastest Cache plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.2.6 via the specificDeleteCache function. This makes it possible for authenticated attackers to delete arbitrary files on the server, which can include wp-config.php files of the affected site or other sites in a shared hosting environment.
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 WP Fastest Cache plugin for WordPress contains a directory traversal vulnerability in the specificDeleteCache function affecting versions up to 1.2.6. Authenticated attackers can manipulate file paths to delete arbitrary files on the server, including sensitive files like wp-config.php or files from other sites in shared hosting environments.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 WP Fastest Cache plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the wp-fastest-cache folder, or view the installed plugins list in WordPress admin under Plugins > Installed PluginsAffected if The plugin folder wp-fastest-cache exists in the plugins directory
-
Identify the installed version of WP Fastest CacheOpen the main plugin file (wp-fastest-cache/wpFastestCache.php) and locate the Version header in the plugin comments, or check the version displayed in WordPress admin plugins listAffected if The reported version is 1.2.6 or lower (versions 1.2.7 and later contain the patch)
-
Confirm the specificDeleteCache function is present in the codebaseSearch the plugin files for the function named 'specificDeleteCache' - typically found in the main plugin PHP file or included library filesAffected if The function specificDeleteCache exists in the plugin code (this is the vulnerable function)
-
Inspect for signs of file deletion exploitationCheck for missing or modified critical files such as wp-config.php in the WordPress root directory, or unexpected cache directories/files deletionAffected if Critical files like wp-config.php are missing or modified, or cache files have been unexpectedly deleted
A user is affected if the WP Fastest Cache plugin version is 1.2.6 or lower and the specificDeleteCache function is present in the codebase.
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 dataUpdate WP Fastest Cache to version 1.2.7 or later to patch the directory traversal vulnerability. Ensure a complete site backup is performed before updating, and verify cache functionality works correctly after the update.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4347 — 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-4347 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