CVE-2026-22366
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 Jude jude allows PHP Local File Inclusion.This issue affects Jude: from n/a through <= 1.3.0.
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 vulnerability in the axiomthemes Jude WordPress theme allows attackers to include arbitrary PHP files via unsanitized input in include/require statements. This can lead to remote code execution if the attacker can upload malicious files or access sensitive system files.
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.
-
Verify Jude theme is installedNavigate to wp-content/themes/ in your WordPress installation and check for a folder named 'jude' or 'Jude'. Alternatively, check via WordPress admin under Appearance > Themes.Affected if The Jude theme folder exists in the themes directory.
-
Determine installed Jude theme versionOpen the style.css file in the Jude theme folder (wp-content/themes/jude/style.css) and look for the 'Version:' comment in the file header. Compare this version to any known affected version range.Affected if The theme version is within an unpatched version range, if such a range is known.
-
Inspect theme for file inclusion parametersSearch the theme PHP files (especially in include/ or functions/ subdirectories) for $_GET, $_POST, or $_REQUEST parameters used in include, require, include_once, or require_once statements without proper sanitization.Affected if Unsanitized user input is used in include/require statements.
-
Check for exposed file inclusion endpointsAccess common theme entry points (index.php, functions.php, or any template files) and test query parameters that might accept file paths (e.g., ?file=, ?template=, ?page=). Observe if the application attempts to include arbitrary files.Affected if The theme accepts file path parameters that can be manipulated to include arbitrary files.
-
Review PHP configurationCheck phpinfo() or your php.ini for the allow_url_include setting. Also verify if PHP's open_basedir restriction is properly configured.Affected if allow_url_include is enabled (increases severity) or open_basedir is not configured to restrict file access.
You are affected if the Jude theme is installed and uses unsanitized input in include/require statements, allowing arbitrary file inclusion via URL parameters.
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 Jude theme to the latest patched version. If no patch is available, implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22366 — 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-22366 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