CVE-2026-28013
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 ThemeREX Kratz kratz allows PHP Local File Inclusion.This issue affects Kratz: from n/a through <= 1.0.12.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the ThemeREX Kratz PHP application where improper control of filename parameters in include/require statements allows attackers to include arbitrary local PHP files. The vulnerability affects Kratz versions through 1.0.12 and could enable reading sensitive files or potentially achieving code execution depending on server configuration.
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 the installed Kratz versionLocate the main version file (commonly version.php, index.php, or a config file in the Kratz root directory) and read the version number from it, or check the HTTP Server header if the application reveals version infoAffected if The version number found is 1.0.12 or lower
-
Locate the vulnerable file inclusion codeSearch the Kratz source code for include/require statements that use variable parameters without sanitization, commonly in files within the includes/ or common/ directoriesAffected if Code contains statements like include($_GET['file']) or require($var) without input validation
-
Test for path traversal vulnerabilitySend a crafted HTTP request with a path traversal payload in the file parameter (such as ../../../../etc/passwd or ../../config.php) to common PHP entry pointsAffected if The application returns contents of files outside the web root directory
-
Verify PHP configuration settingsCheck the PHP configuration file (php.ini) or run phpinfo() to inspect the allow_url_include settingAffected if allow_url_include is enabled (set to On) which would allow remote file inclusion in addition to LFI
-
Identify accessible sensitive filesReview the server file permissions and document root structure to determine if files like configuration files, database credentials, or environment files are readable via the LFI vulnerabilityAffected if The web server user has read access to sensitive configuration files that can be traversed and included
A user is affected if running Kratz version 1.0.12 or lower and the application contains vulnerable include/require statements that allow manipulation of filename parameters through HTTP requests.
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 the latest patched version of Kratz if available, or implement strict input validation with allowlist controls on all file inclusion parameters to prevent path traversal. Additionally, disable allow_url_include and review PHP configuration settings.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28013 — 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-2026-28013 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