CVE-2025-26889
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 hockeydata hockeydata LOS hockeydata-los allows PHP Local File Inclusion.This issue affects hockeydata LOS: from n/a through <= 1.2.4.
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 confidencePHP Local File Inclusion vulnerability in hockeydata LOS allows attackers to include arbitrary local files via improper control of filename parameters in include/require statements. This can lead to exposure of sensitive configuration files, source code, or system files.
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.
-
Locate hockeydata LOS installationSearch for directories containing 'hockeydata' or 'los' in web root directories (commonly /var/www, /htdocs, C:\inetpub\wwwroot). Look for files named 'index.php' or 'los.php' within these directories.Affected if hockeydata LOS is installed and accessible via web server
-
Identify installed versionOpen the main PHP entry point (often index.php or a version.php file in the root directory). Look for a version constant or variable defined near the top (e.g., define('VERSION', '1.2.x')).Affected if Version is 1.2.4 or lower (vulnerable range)
-
Confirm PHP is in useCheck for .php file extensions in the hockeydata LOS directory and verify PHP interpreter is installed (php -v on command line or check http response headers for X-Powered-By: PHP).Affected if PHP is the server-side language and the LFI vulnerability applies to PHP include/require statements
-
Inspect include/require statements for unsafe input handlingIn the hockeydata LOS source code, grep for 'include(' or 'require(' patterns followed by variables (e.g., include($_GET['page']).php'). Check if user-controlled input reaches these statements without validation.Affected if File inclusion functions use unsanitized user input (e.g., $_GET, $_POST parameters) directly in the path
-
Verify web exposure of vulnerable endpointsTest if URL parameters like ?file= or ?page= can be manipulated to include local files (e.g., ../../../../etc/passwd). Attempt a benign test with a known local file if authorized.Affected if The application accepts file path parameters via HTTP GET/POST and includes them without validation
If hockeydata LOS version 1.2.4 or lower is installed, PHP is in use, and the application allows user-supplied paths in include/require statements, the environment is affected by this LFI vulnerability.
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 hockeydata LOS to a version beyond 1.2.4 that contains the patch, or implement input validation/sanitization on file inclusion paths to restrict inclusion to allowed directories only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26889 — 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-26889 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