CVE-2026-22363
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 Rhodos rhodos allows PHP Local File Inclusion.This issue affects Rhodos: from n/a through <= 1.3.3.
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 confidenceA Local File Inclusion (LFI) vulnerability in the Rhodos WordPress theme (version 1.3.3 and below) allows attackers to manipulate include/require statements to execute arbitrary PHP files from the local server, potentially leading to code execution.
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 Rhodos theme is installedNavigate to wp-content/themes/ and check for a directory named 'rhodos' or similar. Use command: ls -la /path/to/wp-content/themes/ | grep -i rhodosAffected if The Rhodos theme directory exists in the WordPress themes folder
-
Identify the installed theme versionOpen the theme's style.css file (typically at wp-content/themes/rhodos/style.css) and locate the 'Version:' header in the CSS comment block at the topAffected if The version number listed is 1.3.3 or lower
-
Locate include/require statements using user inputSearch the theme files for patterns like 'include', 'require', 'include_once', or 'require_once' combined with '$_GET', '$_POST', '$_REQUEST', or '$_COOKIE'. Use: grep -rn '\$_\(GET|POST|REQUEST|COOKIE\)' /path/to/wp-content/themes/rhodos/ | grep -i 'include\|require'Affected if Any include or require statements directly use unsanitized user-supplied input from superglobals
-
Verify the vulnerable code path existsExamine the specific files identified in step 3. Check if the include/require statement uses a parameter value directly in the file path without validation, such as: include($_GET['param']); or require($file_dir . $_REQUEST['file']);Affected if The code uses user input directly in file paths without validation, allowlisting, or sanitization
-
Check if the vulnerable parameter is accessibleReview the identified code to determine which query parameters (GET/POST) trigger the include/require. Common parameter names might include 'file', 'page', 'template', 'path', or 'dir' based on typical LFI patterns.Affected if A parameter accessible via HTTP request is used to control which file gets included
If the Rhodos theme version is 1.3.3 or lower AND the theme files contain include/require statements using unsanitized user input from superglobals, the environment is affected by this 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 dataUpdate the Rhodos theme to the latest patched version; as a temporary measure, deploy a WAF or disable the theme until patched.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22363 — 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-22363 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