CVE-2025-49256
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 Sapa sapa allows PHP Local File Inclusion.This issue affects Sapa: from n/a through <= 1.1.14.
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 PHP Local File Inclusion (LFI) vulnerability in thembay Sapa sapa (versions up to 1.1.14) where improper control of filenames in include/require statements allows attackers to include arbitrary PHP files from the server filesystem, potentially leading to remote 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
- 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.
-
Identify if thembay Sapa sapa is installedSearch the web root directory for files containing 'Sapa sapa', 'sapa', or thembay branding. Look for index.php or common PHP files with these identifiers.Affected if The thembay Sapa sapa application is found on the server
-
Determine the installed versionCheck version.php, composer.json, or any version file in the application root for a version number. Also check the header/footer of main PHP pages for version strings.Affected if The installed version is 1.1.14 or lower
-
Locate include/require statements using variable inputSearch PHP source files for include(), require(), include_once(), or require_once() calls where the path contains variables (e.g., include($_GET['page'], include($page), include($_REQUEST['file']).Affected if Variable-based include/require statements are found that could accept user input
-
Verify user input reaches file inclusion functionsExamine the identified include/require code to trace whether GET, POST, or COOKIE parameters flow directly into the file path without sanitization using basename() or realpath().Affected if User-controlled parameters are used in include/require without proper validation (basename/realpath/whitelist)
-
Check PHP configuration for dangerous settingsReview php.ini for allow_url_fopen=On or allow_url_include=On settings.Affected if allow_url_fopen or allow_url_include are enabled (allows remote file inclusion in addition to LFI)
A user is affected if thembay Sapa sapa version 1.1.14 or lower is installed AND the application contains include/require statements where user input flows into the file path without validation using basename(), realpath(), or a whitelist.
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 dataFix the file inclusion vulnerability by implementing strict input validation using basename() or realpath() functions, and/or using a whitelist approach for allowed files; also ensure allow_url_fopen and allow_url_include are disabled in PHP configuration.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49256 — 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-49256 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