CVE-2026-22367
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 AncoraThemes Coworking coworking allows PHP Local File Inclusion.This issue affects Coworking: from n/a through <= 1.6.1.
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 confidenceLocal File Inclusion vulnerability in AncoraThemes Coworking theme allows attackers to include arbitrary local PHP files via unsanitized input in include/require statements. The CVSS 8.1 indicates relatively easy exploitation with significant impact, likely allowing reading of sensitive system files, configuration files, or credentials from the local filesystem.
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 Coworking theme is installedLocate the theme directory (typically /wp-content/themes/coworking/) and check for the existence of theme files such as style.css, functions.php, or index.php within that folder.Affected if The coworking theme directory exists and contains theme files.
-
Determine the installed theme versionOpen the theme's style.css file (usually at /wp-content/themes/coworking/style.css) and locate the 'Version:' comment in the file header. Compare this version number to 1.6.1.Affected if The installed version is 1.6.1 or lower.
-
Identify vulnerable file inclusion codeSearch PHP files within the theme directory for include, require, include_once, or require_once statements that use variable parameters (e.g., include($filename), require($_GET['file']). Look for patterns where user-controlled input reaches file inclusion functions.Affected if PHP files in the theme contain dynamic file inclusion statements using unsanitized variables.
-
Verify the vulnerable parameter is accessibleIf the file inclusion code uses GET or POST parameters (such as 'file', 'page', 'template', or 'filename'), test whether these parameters can be manipulated through HTTP requests to include arbitrary files.Affected if The application accepts and processes file path parameters without proper validation.
You are affected if the Coworking theme version is 1.6.1 or lower AND the theme contains vulnerable file inclusion code that accepts user-controlled 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 dataImplement strict whitelist-based validation for any file paths used in include/require statements, ensuring only permitted files can be loaded. Remove or disable any dynamic file inclusion functionality that uses user-supplied input.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22367 — 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-22367 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