CVE-2025-46468
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 WPFable Fable Extra fable-extra allows PHP Local File Inclusion.This issue affects Fable Extra: from n/a through <= 1.0.6.
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 PHP Local File Inclusion vulnerability in WPFable Fable Extra allows attackers to include arbitrary local files via unsanitized input in include/require statements, potentially leading to arbitrary code execution.
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
- 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.
-
Confirm WPFable Fable Extra installationSearch the web root directory for Fable Extra files (e.g., check for fable-extra.php, or a directory named fable-extra)Affected if The product is not present in the environment, the user is not affected by this CVE
-
Determine installed versionLocate version information in the Fable Extra source files (typically in a header comment, README, or version constant) and compare against any known patched versionAffected if The installed version matches the vulnerable version range (if any) and no patch has been applied
-
Identify vulnerable file inclusion patternsSearch PHP files in the Fable Extra directory for include, include_once, require, or require_once statements that use variables (e.g., include($_GET['file']) or require($path)) without sanitizationAffected if Unsanitized user-controlled input is used directly in include/require statements within the Fable Extra code
-
Verify input reaches file inclusionTrace the data flow from HTTP request parameters to the include/require statements to confirm user input can reach the file inclusion functionAffected if User-supplied input from GET, POST, or COOKIE parameters can reach the vulnerable include/require call without validation
-
Check application exposes file inclusion functionalityIdentify which PHP scripts handle file path parameters and are accessible via web requests (check routing or entry points)Affected if The vulnerable file inclusion code is accessible via web request and can be triggered by an attacker
The environment is affected if WPFable Fable Extra is installed and its PHP code contains include/require statements using unsanitized user input that can be triggered via web requests.
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 to a patched version of Fable Extra. If no patched version exists, implement strict whitelist-based input validation for all file inclusion operations and disable allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46468 — 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-46468 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