CVE-2025-39461
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Nawawi Jamili Docket Cache docket-cache allows PHP Local File Inclusion.This issue affects Docket Cache: from n/a through <= 24.07.02.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the Docket Cache WordPress plugin. The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to read sensitive files from the server's filesystem. This affects all versions through 24.07.02.
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 Docket Cache plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Docket Cache' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'docket-cache'.Affected if The Docket Cache plugin is present on the WordPress site.
-
Check installed version numberIn WordPress admin, find Docket Cache in the Plugins list and view the version number under the plugin name. Alternatively, open the plugin's main PHP file (usually docket-cache.php) and look for the 'Version' header comment in the file's metadata.Affected if The installed version is 24.07.02 or any earlier version.
-
Identify PHP include/require usage in plugin filesSearch the plugin directory (/wp-content/plugins/docket-cache/) for PHP include, include_once, require, or require_once statements that reference variables in the path, such as: include($something); require($path); include_once($_GET['parameter']); or similar patterns.Affected if Any include/require statement uses unsanitized user input (like $_GET, $_POST, or other request parameters) to construct file paths.
-
Check for exposed file path parametersReview plugin PHP files for parameters passed via URL query strings (e.g., ?file=..., ?path=..., ?page=...) that are subsequently used in include/require statements without validation.Affected if The plugin accepts file path parameters from HTTP requests and includes them without sanitizing the path to prevent directory traversal (e.g., ../../).
A site is affected if Docket Cache version 24.07.02 or earlier is installed AND the plugin contains PHP include/require logic that uses unsanitized request parameters to load files, allowing directory traversal 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 dataUpdate Docket Cache to the latest version beyond 24.07.02 once a patch is released. As a temporary mitigation, implement strict input validation on any user-controlled file path parameters and consider deploying a WAF to block known LFI attack patterns.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39461 — 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-2025-39461 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