CVE-2026-22452
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 ThemeREX Hoverex hoverex allows PHP Local File Inclusion.This issue affects Hoverex: from n/a through <= 1.5.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 · high confidenceA PHP Local File Inclusion vulnerability exists in ThemeREX Hoverex (versions <= 1.5.10) due to improper control of filenames in include/require statements. The vulnerability allows attackers to include arbitrary local files via user-controlled input, 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.
-
Locate ThemeREX Hoverex installationSearch your web server's document root for directories or files containing 'hoverex' or 'themrex' in the name. Common paths include /wp-content/plugins/ or /wp-content/themes/ if this is a WordPress component.Affected if ThemeREX Hoverex is found installed on the server
-
Identify the installed versionCheck version.php, readme.txt, or style.css within the Hoverex plugin/theme directory for a version number. Compare it against the affected range of versions <= 1.5.10.Affected if The installed version is 1.5.10 or lower
-
Inspect include/require statements for user inputExamine PHP files in the Hoverex directory, specifically looking for include(), require(), include_once(), or require_once() statements that incorporate request parameters (e.g., $_GET, $_POST) without sanitization.Affected if The code uses raw request parameters in include/require paths without validation or path sanitization
-
Check for directory traversal vulnerabilitiesIf the previous check finds vulnerable include/require patterns, test whether the parameter accepts path traversal sequences like ../../ to access files outside the intended directory.Affected if The include/require accepts unsanitized user input allowing ../../ sequences to navigate the filesystem
-
Verify remote access to vulnerable scriptConfirm the vulnerable PHP file is accessible via the web server without authentication. Attempt to access a known PHP file in the installation that uses the include/require with user input.Affected if The vulnerable script is reachable over HTTP/HTTPS without authentication
If ThemeREX Hoverex version 1.5.10 or lower is installed and its PHP files use unsanitized request parameters in include/require statements that are web-accessible, the environment is affected by this LFI vulnerability.
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 dataRemove or disable the vulnerable ThemeREX Hoverex plugin/theme until a vendor patch is available; implement strict input validation and path sanitization for any include/require statements to prevent directory traversal.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22452 — 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-22452 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