CVE-2023-26005
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 BZOTheme Fitrush allows PHP Local File Inclusion. This issue affects Fitrush: from n/a through 1.3.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 · moderate confidenceA Local File Inclusion (LFI) vulnerability exists in the BZOTheme Fitrush (versions up to 1.3.4) where improper validation of filename parameters in PHP include/require statements allows attackers to read arbitrary local files by manipulating path traversal sequences.
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 BZOTheme Fitrush installationSearch for theme directory named 'Fitrush' or 'bzo' in the web application's theme or template folder. Look for files like theme.php, header.php, or index.php containing 'Fitrush' or 'bzo' branding strings.Affected if The BZOTheme Fitrush theme is present in the web application
-
Determine installed Fitrush versionOpen the main theme PHP file (typically theme.php, index.php, or a version/info file within the Fitrush theme directory) and locate the version declaration. Compare the version number to the affected range (versions up to 1.3.4).Affected if The installed version is 1.3.4 or lower
-
Locate PHP file inclusion statementsSearch the Fitrush theme directory for PHP files containing include, include_once, require, or require_once statements. Focus on files that accept filename or path parameters via $_GET, $_POST, or other user-supplied input.Affected if PHP files use include/require with dynamic file paths derived from user input
-
Inspect input validation on file parametersExamine the identified include/require statements in source code. Check whether the parameter controlling the file path is validated with functions like basename(), realpath(), or whitelist checking before being used in the include/require.Affected if File path parameters are used directly in include/require without proper validation or sanitization
-
Test for path traversal vulnerabilityIf dynamic file inclusion is present, attempt to access the vulnerable endpoint with path traversal sequences such as ../../../../etc/passwd or similar. Observe whether the application returns content from files outside the intended directory.Affected if The application returns content from files outside the intended directory when path traversal sequences are supplied
A user is affected if BZOTheme Fitrush version 1.3.4 or lower is installed and PHP files contain include/require statements using user-supplied file path parameters without proper 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 dataImplement strict input validation with whitelist approach for file inclusion paths, use basename() to strip directory traversal sequences, and ensure all file inclusion uses fixed paths rather than user-supplied input.
- 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-2023-26005 — 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-2023-26005 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