CVE-2026-22338
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 · uneditedUnauthenticated Local File Inclusion in EcoBlue <= 1.15 versions.
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 confidenceUnauthenticated Local File Inclusion (LFI) vulnerability in EcoBlue CMS versions 1.15 and below allows remote attackers to read sensitive files on the server filesystem without any authentication credentials, potentially exposing configuration files, credentials, or other sensitive data.
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.
-
Confirm EcoBlue CMS installationLook for EcoBlue CMS files in the web root directory. Check for characteristic files such as index.php, admin/, or configuration files bearing the EcoBlue name. Use file system inspection or directory listing commands to identify the presence of EcoBlue-specific files and folder structure.Affected if EcoBlue CMS files are found in the web directory structure
-
Determine installed EcoBlue versionLocate the version file or version identifier within the EcoBlue installation. Common locations include a VERSION file, version in the main index.php, admin/config.php, or within the CMS footer/source code. Compare the discovered version number to the affected range of 1.15 and below.Affected if The installed version is 1.15 or any version below 1.15
-
Identify file inclusion parametersReview the application source code for parameters that accept file paths or names, such as those used in include(), require(), fopen(), or similar functions. Pay particular attention to parameters that might handle template loading, page rendering, or configuration file selection.Affected if Parameters accepting user-controlled file paths are found without proper sanitization
-
Test for unauthenticated directory traversalSend HTTP requests to suspected LFI endpoints with directory traversal sequences such as ../../../../etc/passwd or similar paths. Since this is an unauthenticated LFI, these requests should not require any authentication headers or session cookies.Affected if Directory traversal sequences successfully return file contents without authentication
If EcoBlue CMS version 1.15 or below is installed and running, the environment is affected by this unauthenticated 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 EcoBlue to a version newer than 1.15. If no update is available, implement strict input validation and use allow-lists for file path parameters to prevent directory traversal sequences.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22338 — 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-22338 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