CVE-2026-22495
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 Greenville greenville allows PHP Local File Inclusion.This issue affects Greenville: from n/a through <= 1.3.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 confidenceA PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Greenville WordPress theme (versions up to 1.3.2) allows attackers to manipulate filename parameters in include/require statements to execute arbitrary local PHP files, potentially 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.
-
Identify Greenville theme versionLocate the theme's style.css file in wp-content/themes/greenville/ and look for the 'Version:' header in the file comments, or check via WordPress admin dashboard under Appearance > ThemesAffected if The version listed is 1.3.2 or lower (any version up to and including 1.3.2)
-
Confirm theme is activeCheck if the Greenville theme is the currently active theme by inspecting wp_options table for 'template' or 'stylesheet' values, or via WordPress admin dashboardAffected if The Greenville theme is installed and active on the WordPress site
-
Inspect PHP files for unsafe include/require usageSearch PHP files in the theme directory (wp-content/themes/greenville/) for include, include_once, require, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without proper sanitizationAffected if Any PHP file contains include/require statements with unsanitized user input from request parameters
-
Identify the vulnerable parameterLook for code patterns where file paths are constructed using parameters like 'file', 'page', 'template', 'slug', or similar names from URL parameters, passed directly to include/require without validation functions like basename() or realpath()Affected if The theme contains code that directly uses user-supplied parameters in file inclusion functions without path validation
A user is affected if the Greenville WordPress theme version is 1.3.2 or lower AND the theme contains PHP code that uses unsanitized request parameters in include/require statements.
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 Greenville theme to a patched version immediately. If no patched version is available, disable or remove the theme until a fix is released.
- 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-22495 — 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-22495 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