CVE-2026-22365
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 axiomthemes Soleng soleng allows PHP Local File Inclusion.This issue affects Soleng: from n/a through <= 1.0.5.
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 confidenceLocal File Inclusion (LFI) vulnerability in the axiomthemes Soleng theme allows attackers to manipulate include/require statements to load arbitrary local PHP files. The lack of proper input validation on file path parameters enables reading sensitive files or potentially achieving remote code execution if attacker-controlled files can be uploaded.
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 if the Soleng theme is installedLocate the theme directory - typical path is wp-content/themes/soleng/ or similar. Check for a style.css file containing 'Theme Name: Soleng' or 'Template: soleng'Affected if The Soleng theme by axiomthemes is present in the WordPress themes directory
-
Determine the installed Soleng theme versionOpen the style.css file in the theme directory and read the 'Version:' header field. Compare this version against any known affected version rangesAffected if The installed version falls within a vulnerable range (if version data becomes available) or cannot be determined
-
Search for dynamic file inclusion patterns in PHP filesUse grep or a text search to find PHP files containing 'include(', 'require(', 'include_once(', or 'require_once(' with variables as path arguments, for example: include($_GET['...']) or require($path)Affected if Dynamic file inclusion statements that accept user-supplied input as path parameters are found in theme PHP files
-
Inspect the file inclusion parameters for input validationReview the identified include/require statements to determine if the variables are sanitized, use whitelist validation, or are passed through functions like basename() or realpath() before inclusionAffected if No input validation, sanitization, or whitelist approach is applied to file path parameters before inclusion
-
Verify if the vulnerable parameters are accessible via HTTP requestsCheck if the file inclusion parameters originate from $_GET, $_POST, or $_REQUEST superglobals, and determine if they can be controlled through URL parameters or form inputsAffected if The file path parameters can be controlled through external HTTP requests without proper filtering
A user is affected if the Soleng theme is installed and contains dynamic include/require statements that accept unsanitized user-controlled input for file paths.
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 whitelist-based validation for file inclusion paths and disable allow_url_include. Replace dynamic includes with a whitelist of permitted files, or use a switch/case structure with predefined values instead of user-supplied input.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22365 — 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-22365 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