CVE-2025-49251
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 thembay Fana fana allows PHP Local File Inclusion.This issue affects Fana: from n/a through <= 1.1.28.
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 · moderate confidenceA PHP Local File Inclusion vulnerability exists in thembay Fana fana (version <= 1.1.28) where user-supplied input is improperly used in include/require statements without sufficient validation, allowing attackers to include arbitrary files from the server filesystem.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 the thembay Fana fana version installedLocate the version file, readme, or header that declares the software version (commonly found in composer.json, version.php, or a changelog file)Affected if The installed version is 1.1.28 or lower
-
Identify PHP files containing include or require statements with dynamic inputSearch the codebase for PHP files that use include, require, include_once, or require_once where the path is built from a variable (for example: include($var), include($_GET['param']))Affected if Such dynamic include/require patterns exist in the codebase
-
Inspect parameters used in include/require for lack of validationExamine the identified include/require code for any input validation, such as whitelist checks, basename() usage, or sanitization functions, before the file path is usedAffected if User-supplied parameters flow directly to include/require without sanitization or validation checks
-
Confirm the web server runs PHP and accepts user inputVerify PHP is enabled on the server and that the application accepts request parameters (GET, POST, or COOKIE) that could be passed to the vulnerable include/require logicAffected if PHP is active and the application accepts user input that reaches the vulnerable include/require code
A user is affected if thembay Fana fana version 1.1.28 or lower is installed AND the codebase contains PHP include/require statements that use unsanitized user input without validation.
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 dataImplement strict whitelist-based input validation for any parameters used in include/require statements, and use basename() to strip directory traversal sequences. Consider migrating to a safe include pattern that doesn't use user input in file paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49251 — 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-49251 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