CVE-2025-26757
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 FULL SERVICES FULL Customer full-customer allows PHP Local File Inclusion.This issue affects FULL Customer: from n/a through <= 3.1.26.
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 confidencePHP Local File Inclusion vulnerability in the full-customer component allows attackers to include arbitrary files from the server's filesystem by manipulating input parameters used in PHP include/require statements. The vulnerability exists in versions through 3.1.26 and could be exploited to read sensitive system files, potentially leading to 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
- 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.
-
Identify full-customer component installationSearch the web server filesystem for the full-customer component directories or files. Common locations include /var/www/html/, /app/, or the document root. Look for directories or files named 'full-customer', 'customer', or similar naming patterns.Affected if The full-customer component is present on the server
-
Determine the installed versionLocate version information files such as composer.json, version.php, CHANGELOG, or a dedicated version file within the full-customer component directory. Check the file contents for a version number.Affected if The installed version is 3.1.26 or any earlier version through unknown earlier versions
-
Identify PHP include/require usageSearch the full-customer component source code for dynamic include, require, include_once, or require_once statements that use variables or request parameters. Use grep or similar tools: grep -r 'include\|require' --include='*.php' .Affected if Dynamic file inclusion using variables or user-supplied input is present in the code
-
Check for vulnerable parameter handlingExamine the identified include/require statements for lack of sanitization. Look for code patterns where $_GET, $_POST, or $_REQUEST parameters are used directly in include/require without basename(), realpath(), or whitelist validation.Affected if User-controlled input flows directly into include/require statements without validation
-
Inspect server configuration for exposureReview the web server configuration (Apache/nginx) to confirm the full-customer component is web-accessible. Check if PHP file execution is enabled in the component's directory.Affected if The component is web-accessible with PHP execution enabled
A system is affected if the full-customer component version is 3.1.26 or earlier AND the vulnerable dynamic file inclusion pattern with unsanitized user input exists 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 dataImplement strict input validation with whitelist approach for file inclusion paths, disable allow_url_include, use basename() and realpath() to normalize paths and prevent directory traversal sequences (..), and refactor vulnerable include/require statements to use static paths.
- Consultation6.0 h
- Implementation4.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 $4,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26757 — 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-26757 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