CVE-2026-22376
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 Parkivia parkivia allows PHP Local File Inclusion.This issue affects Parkivia: from n/a through <= 1.1.9.
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 (LFI) vulnerability in the AncoraThemes Parkivia WordPress theme allows attackers to include arbitrary local PHP files through unsanitized user input in include/require statements, potentially leading to code execution or sensitive data exposure.
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 Parkivia theme is installedNavigate to Appearance > Themes in WordPress admin panel, or inspect /wp-content/themes/ directory for the parkivia theme folderAffected if Parkivia theme folder exists in the WordPress themes directory
-
Identify installed Parkivia theme versionCheck the style.css file in /wp-content/themes/parkivia/ for the 'Version' header, or view theme details in WordPress admin under Appearance > ThemesAffected if Version is older than the latest patched version or version cannot be determined (assume vulnerable)
-
Locate vulnerable include/require code patternsSearch theme PHP files for include/require statements using user input: grep -r 'include.*\$_' and grep -r 'require.*\$_' in /wp-content/themes/parkivia/ directoryAffected if Files contain include/require statements that directly use $_GET, $_POST, or $_REQUEST parameters without sanitization
-
Check for directory traversal patterns in requestsReview theme PHP files for usage of basename(), realpath(), or similar path normalization functions before include/require statementsAffected if No path sanitization functions are used, or sanitization is missing before file inclusion
Environment is affected if the Parkivia WordPress theme is installed and its code contains 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 dataUpgrade to the latest version of Parkivia theme which should contain patches for proper input validation, or implement Web Application Firewall (WAF) rules to block directory traversal patterns in request parameters.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22376 — 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-22376 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