CVE-2026-22496
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 Hypnotherapy hypnotherapy allows PHP Local File Inclusion.This issue affects Hypnotherapy: from n/a through <= 1.2.10.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Hypnotherapy WordPress theme. The vulnerability allows attackers to manipulate filename parameters in PHP include/require statements to read arbitrary local files from the server filesystem, potentially exposing sensitive configuration files, credentials, or system 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 Hypnotherapy theme is installedAccess WordPress admin dashboard, go to Appearance > Themes, or inspect /wp-content/themes/ directory for a folder named 'hypnotherapy' or similarAffected if The AncoraThemes Hypnotherapy theme is present in the WordPress installation
-
Determine the installed theme versionCheck the theme's style.css file in the theme folder for the 'Version:' header, or look in the WordPress admin theme details panelAffected if The version number cannot be determined or is earlier than the patched release
-
Locate PHP files handling file inclusionSearch the theme folder for PHP files containing include, require, include_once, or require_once statements, especially those using variables in the path like include($file) or require($_GET['filename'])Affected if Files with dynamic file inclusion using user-supplied parameters are found
-
Inspect file inclusion parameters for LFI patternsReview identified PHP files for insecure patterns where filename/path parameters from $_GET, $_POST, or other user input are directly used in include/require statements without sanitizationAffected if Parameters used in file inclusion are not validated against a whitelist or sanitized
-
Test the vulnerability if accessibleIf the vulnerable parameter is identified, attempt a benign LFI test by including a known file like /etc/passwd (with appropriate URL encoding) to confirm the file can be readAffected if The server returns contents of files outside the theme directory, confirming the LFI is exploitable
The site is affected if the Hypnotherapy theme is installed and contains PHP files with unauthenticated, user-controlled parameters used directly in include/require statements without input validation.
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 dataFix the vulnerable include/require statements to use whitelisted file paths, implement strict input validation on any user-controlled parameters used in file inclusion, and ensure PHP's allow_url_include is disabled. Upgrading to a patched version of the theme is recommended.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22496 — 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-22496 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