CVE-2026-22372
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 Isida isida allows PHP Local File Inclusion.This issue affects Isida: from n/a through <= 1.4.2.
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 confidenceThe AncoraThemes Isida plugin (versions up to 1.4.2) contains a PHP Local File Inclusion vulnerability where user-supplied input is used in include/require statements without proper validation. An unauthenticated attacker could potentially include malicious PHP files from the server, 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.
-
Verify Isida plugin installationLocate the Isida plugin files in the WordPress wp-content/plugins directory or check the theme files if this is bundled with an AncoraThemes theme. Look for files named isida.php or directories containing 'isida' in the path.Affected if The Isida plugin or theme component from AncoraThemes is present on the WordPress installation.
-
Identify the installed versionCheck the main plugin file (typically isida.php) or the style.css file within the theme for the 'Version:' header comment. Alternatively, check any readme.txt or plugin metadata that states the version number.Affected if The installed version is 1.4.2 or any earlier version.
-
Locate file inclusion codeSearch the Isida plugin files for include(), require(), include_once(), or require_once() statements that use variables derived from user input such as $_GET, $_POST, $_REQUEST, or any parameter that could be attacker-controlled.Affected if Code exists that uses include or require with user-supplied variables without validation.
-
Verify lack of input validationExamine the file inclusion code found in the previous step. Check whether the included file path undergoes any validation, sanitization, or whitelist checking before being used in the include/require statement.Affected if The file inclusion uses raw user input without any validation, sanitization, or whitelist filtering.
-
Confirm parameter accessibilityDetermine if the vulnerable parameter can be accessed without authentication. Check if the file inclusion code is reachable without requiring login or any form of access control.Affected if The vulnerable file inclusion parameter is accessible to unauthenticated users (no login required).
A user is affected if the Isida plugin/theme version is 1.4.2 or lower AND the vulnerable file inclusion code exists and is accessible without authentication.
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 input validation using a whitelist approach for all file inclusion operations, disable allow_url_fopen and allow_url_include in php.ini, and ensure all include/require paths use whitelisted static values rather than user-controlled variables.
- 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-22372 — 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-22372 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