CVE-2026-22375
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 Impacto Patronus impacto-patronus allows PHP Local File Inclusion.This issue affects Impacto Patronus: from n/a through <= 1.2.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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Impacto Patronus theme (versions up to 1.2.3) allows remote attackers to include arbitrary PHP files from the server by manipulating file inclusion parameters without proper input validation. This could lead to code execution or sensitive file disclosure.
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 Impacto Patronus theme is installedLocate the theme directory - typically in wp-content/themes/impacto-patronus or similar path depending on WordPress installation. Check for existence of style.css or theme files containing 'Impacto Patronus' or 'AncoraThemes' metadata.Affected if The theme is present in the WordPress themes directory
-
Determine the installed versionOpen the theme's style.css or functions.php file and look for the Version: header comment, or check for a version constant defined in the theme's main PHP files.Affected if Version is 1.2.3 or lower (including any 1.x version up to 1.2.3)
-
Locate PHP files using include/require with dynamic inputSearch the theme directory for PHP files containing include, require, include_once, or require_once statements where variables or superglobals ($_GET, $_POST, $_REQUEST, etc.) are used directly in the path parameter.Affected if Files exist that use unsanitized user input in include/require statements
-
Verify user-controllable input reaches file inclusionExamine the identified include/require calls to confirm that parameters from $_GET, $_POST, $_REQUEST, or similar are passed directly to the include/require without sanitization functions like basename(), realpath(), or allowlist validation.Affected if User-supplied parameters can control which file gets included without validation
-
Test if directory traversal is possibleIf the vulnerability exists, attempt to include files outside the theme directory using paths like ../../../../etc/passwd or similar traversal sequences in the vulnerable parameter.Affected if The include/require allows traversal outside the intended directory
A user is affected if they have AncoraThemes Impacto Patronus version 1.2.3 or lower installed AND their theme code contains PHP include/require statements that use unsanitized user input from request 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 allowlist-based input validation on all file inclusion parameters, using basename() and realpath() to sanitize paths, and avoid using user-supplied input directly in include/require statements. Consider upgrading to a patched version if available.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22375 — 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-22375 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