CVE-2026-22516
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 Wizor's wizors-investments allows PHP Local File Inclusion.This issue affects Wizor's: from n/a through <= 2.12.
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 exists in AncoraThemes Wizor's wizors-investments theme (versions <= 2.12) where the application fails to properly validate user-supplied input before using it in include/require statements, allowing attackers to read sensitive local files or potentially achieve code execution by including malicious PHP files.
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 Wizor's theme is installedLocate the theme directory - typically at wp-content/themes/wizors-investments/ or search for files containing 'wizors-investments' in the themes folderAffected if The wizors-investments theme directory exists on the server
-
Determine the installed theme versionCheck the theme's style.css file (usually in the theme root) for the 'Version:' header, or check for a version.php/changelog file within the themeAffected if The version is 2.12 or lower, or the version cannot be determined (indicating an outdated installation)
-
Inspect include/require statements for unsafe input usageSearch the theme's PHP files (particularly in functions.php, template files, and any files handling page requests) for patterns like 'include($_GET', 'require($_GET', 'include($_REQUEST', 'require($_POST' without proper validationAffected if Any include or require statement uses $_GET, $_POST, or $_REQUEST directly without sanitization or validation checks
-
Check for vulnerable parameter patterns in URL-handling codeReview PHP files that handle page/template routing - look for parameters used in include/require calls (e.g., '?page=', '?template=') and verify if they are validated before useAffected if URL parameters are used in include/require statements without validation or whitelist checks
-
Review PHP configuration for dangerous settingsCheck php.ini or use phpinfo() to verify the allow_url_include setting is enabled (value should be 1 or On)Affected if allow_url_include is enabled, which would allow remote file inclusion in addition to local file inclusion
The environment is affected if the wizors-investments theme version is 2.12 or lower, AND the theme contains include/require statements using unsanitized user input from $_GET, $_POST, or $_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 dataUpdate the Wizor's theme to a patched version if available; otherwise, implement strict input validation on include/require statements and ensure PHP's allow_url_include setting is disabled.
- 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-22516 — 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-22516 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