CVE-2026-28128
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 Verse verse allows PHP Local File Inclusion.This issue affects Verse: from n/a through <= 1.7.0.
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 confidenceThe ThemeREX Verse WordPress theme contains a PHP Local File Inclusion vulnerability where the application does not properly validate or sanitize user-supplied input before using it in include/require statements. An attacker could potentially exploit this to include arbitrary PHP files from the server or, depending on configuration, remote 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 installed ThemeREX Verse versionLocate the theme's style.css file in wp-content/themes/themrex-verse/ and read the 'Version:' header, or check theme.json if presentAffected if Version is 1.7.0 or lower (any version prior to the patched release)
-
Locate vulnerable include/require patternsSearch PHP files in the theme directory for include, require, include_once, or require_once statements that reference $_GET, $_POST, or $_REQUEST variables without validationAffected if Any include/require statement uses raw user input without sanitization or allowlist validation
-
Identify the vulnerable parameterExamine the PHP files found in step 2 to identify which specific request parameter (e.g., 'file', 'path', 'template', 'page') is passed to the include/require without validationAffected if A request parameter is directly used in an include/require statement without validation (e.g., include($_GET['file']);)
-
Test parameter accessibilitySend a crafted request to the WordPress site using the identified parameter (e.g., ?file=../../../../wp-config.php or ?file=/etc/passwd) to confirm if arbitrary file inclusion is possibleAffected if The server returns content from files outside the theme directory, indicating the LFI is exploitable
-
Check for remote file inclusionTest with a remote URL (e.g., ?file=http://example.com/malicious.txt) to determine if remote files can be included if allow_url_include is enabledAffected if The server attempts to fetch or include content from a remote URL, indicating RFI capability in addition to LFI
If the ThemeREX Verse theme version is 1.7.0 or lower and any PHP file in the theme directly uses user-supplied request parameters in include/require statements without validation, the environment is vulnerable to CVE-2026-28128.
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 dataUpgrade to a patched version of ThemeREX Verse beyond 1.7.0. If no patch is available, implement input validation with an allowlist approach on any parameters used in include/require statements, or disable PHP file inclusion functionality entirely if not required.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28128 — 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-28128 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