CVE-2026-28058
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 Dixon dixon allows PHP Local File Inclusion.This issue affects Dixon: from n/a through <= 1.4.2.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 confidenceThe ThemeREX Dixon WordPress theme through version 1.4.2.1 contains a PHP Local File Inclusion (LFI) vulnerability. Attackers can manipulate parameters in include/require statements to include arbitrary PHP files from the server, potentially achieving remote 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 installed ThemeREX Dixon versionLocate the theme in wp-content/themes/dixon/ and open style.css. Look for the 'Version:' header in the theme comments at the top of the file.Affected if Version is 1.4.2.1 or lower (the version number in style.css is less than or equal to 1.4.2.1)
-
Search for vulnerable include/require patternsIn the theme directory, use grep or a text editor to search for include, include_once, require, or require_once statements that use variables in the path (e.g., include($some_var), require_once($_GET['param']), etc.).Affected if Any include/require statements reference variables without sanitization, particularly in files under the include/ directory
-
Inspect include directory for LFI entry pointsExamine PHP files in the include/ folder of the theme. Look for parameters passed to include/require that could be controlled via GET or POST requests.Affected if Files in include/ accept user input (from $_GET, $_POST, $_REQUEST) and pass it directly to include/require without validation
-
Check for path traversal patternsSearch for patterns like '../' or variable concatenation in include statements. Look for code that fails to whitelist allowed files before inclusion.Affected if The code allows path traversal sequences or does not restrict which files can be included
-
Verify external access to vulnerable codeDetermine if the vulnerable include files are accessible directly via web requests. Check if they require authentication or are protected by WordPress logic.Affected if The vulnerable include files can be accessed without authentication (no is_user_logged_in check, no admin capability check)
-
Test for actual LFI exploitationIf accessible, attempt a safe test inclusion of a known file (e.g., ../../wp-config.php) using a controlled parameter to confirm the vulnerability exists.Affected if Including a known file outside the theme directory succeeds, confirming path traversal is possible
You are affected if the ThemeREX Dixon theme version is 1.4.2.1 or lower AND vulnerable include/require patterns exist that accept user input without sanitization and are web-accessible.
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.
dbcve · scopedUpdate ThemeREX Dixon to the latest patched version. If no patch is available, refactor vulnerable include/require statements to use whitelisted file paths and implement strict input validation to prevent path traversal.
Latest available ThemeREX Dixon theme version (check WordPress theme repository or ThemeREX for version newer than 1.4.2.1)
- 1. Update the ThemeREX Dixon theme to the latest available version from the official WordPress theme repository or ThemeREX vendor
- 2. Verify the update does not introduce compatibility issues with your WordPress version and active plugins
- 3. After updating, test critical site functionality to ensure the theme works correctly
- 4. Review server logs for any signs of exploitation attempts targeting the LFI vulnerability
- 5. Consider implementing additional web application firewall (WAF) rules to block suspicious file inclusion requests
Generated from the published advisory — verify against the referenced sources before acting.
- 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-28058 — 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-28058 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