CVE-2025-27015
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 designingmedia Hostiko hostiko allows PHP Local File Inclusion.This issue affects Hostiko: from n/a through < 30.1.
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 (LFI) vulnerability in the Hostiko template allows attackers to manipulate file inclusion paths to read arbitrary files from the server. The vulnerability exists due to improper control of filenames in include/require statements, affecting versions prior to 30.1.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Hostiko template versionLook for a version file, changelog, or configuration file in the template directory (common locations: version.php, changelog.txt, or in the main template PHP files where version may be defined as a constant)Affected if The version found is earlier than 30.1, or no version file is located and the template appears to be an older release
-
Locate PHP files with include/require statementsSearch the template directory for PHP files containing include, require, include_once, or require_once statements - examine files in the root and subdirectories for dynamic file inclusion patternsAffected if Dynamic file inclusion is found where file paths are constructed from user input or request parameters without sanitization
-
Check for controllable file inclusion parametersInspect PHP files for parameters (such as $_GET, $_POST, or similar) used directly in include/require statements without validation - look for patterns like 'include($_GET["page"])' or 'require($param)'Affected if User-controllable parameters are used in include/require statements without proper validation or whitelisting, allowing path traversal (e.g., ../../etc/passwd)
-
Verify path traversal is possibleIf vulnerable include patterns are found, test whether directory traversal sequences (../) can be used to access files outside the intended directory - examine the code for lack of basename(), realpath(), or whitelist validationAffected if The code allows path traversal sequences in the parameter without validation, making arbitrary file读取 possible
You are affected if the Hostiko template version is earlier than 30.1 AND the template contains PHP files with dynamic include/require statements that accept user-controllable 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 dataUpgrade to Hostiko version 30.1 or later, and implement strict input validation/whitelisting on all file inclusion parameters to prevent path traversal attacks.
- 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-27015 — 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-27015 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