CVE-2026-22443
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 Alliance alliance allows PHP Local File Inclusion.This issue affects Alliance: from n/a through <= 3.1.1.
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 ThemeREX Alliance plugin versions through 3.1.1 allows attackers to include arbitrary PHP files from the server due to improper control of filename parameters in include/require statements. This can lead to code execution, information disclosure, or privilege escalation.
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.
-
Confirm ThemeREX Alliance plugin installationCheck your WordPress plugins directory or examine the plugin files for the presence of the ThemeREX Alliance plugin. Look for directories or files containing 'trx-alliance' or 'themerex-alliance' in the wp-content/plugins path.Affected if The plugin directory or files exist on the server.
-
Identify installed versionLocate the main plugin PHP file (commonly named index.php, main.php, or similar within the plugin directory) and search for a version constant or header comment that declares the plugin version.Affected if The version is 3.1.1 or any earlier version (the vulnerability affects all versions through 3.1.1).
-
Check web server configuration for directory traversalReview your web server (Apache/Nginx) configuration for AllowOverride settings and ensure that .htaccess files can override restrictions. Verify that PHP configuration does not have open_basedir restrictions configured to limit file access.Affected if The web server permits .htaccess overrides or lacks open_basedir restrictions, making directory traversal exploitation feasible.
-
Inspect for vulnerable include/require patternsExamine the plugin PHP source code for include(), require(), include_once(), or require_once() statements that use user-supplied input (such as GET/POST parameters) without proper sanitization, particularly where the input could contain directory traversal sequences.Affected if The plugin code contains include/require statements using unsanitized input that could accept paths like ../ or null byte sequences.
The environment is affected if ThemeREX Alliance plugin version 3.1.1 or earlier is installed and the web server configuration permits directory traversal exploitation of the vulnerable include/require patterns.
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 ThemeREX Alliance to the latest patched version immediately. If no update is available, disable the plugin/theme and implement web application firewall rules to block directory traversal patterns (e.g., ../, null byte injection). Review and harden PHP configuration settings.
- 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-22443 — 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-22443 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