CVE-2026-28032
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 Tuning tuning allows PHP Local File Inclusion.This issue affects Tuning: from n/a through <= 1.3.
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 confidenceLocal File Inclusion vulnerability in ThemeREX Tuning plugin allows attackers to manipulate filename parameters in PHP include/require statements, potentially enabling arbitrary PHP code execution through path traversal.
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.
-
Verify ThemeREX Tuning plugin is installedCheck the WordPress plugin directory for the ThemeREX Tuning plugin files, or list all installed plugins via wp-cli: wp plugin list --status=active --format=csvAffected if ThemeREX Tuning plugin is present and active in the WordPress installation
-
Identify the installed plugin versionRead the plugin main file header (usually in wp-content/plugins/trex-tuning/ or similar naming) to find the Version: field, or use: wp plugin get trex-tuning --format=jsonAffected if Version cannot be determined or is unknown/unpatched (no fix version provided in CVE data)
-
Locate vulnerable include/require statementsSearch plugin PHP files for dynamic include/require/require_once statements using variables or request parameters, particularly patterns like: include($_GET['filename']) or require($filename) with insufficient sanitizationAffected if Code contains include/require statements that directly use user-supplied input without proper path sanitization or validation
-
Check for accessible parameter endpointsIdentify PHP files that process filename parameters via GET/POST requests. Review URL routing and any files that handle tuning or theme customization featuresAffected if Endpoints accepting filename parameters are accessible without authentication or proper access controls
-
Look for evidence of path traversal exploitationReview web server access logs for patterns like: ../, ..\, /etc/passwd, php://filter, or other traversal sequences in filename-related parameters. Also check for unusual PHP files in uploads or plugin directoriesAffected if Logs show traversal attempts targeting the plugin, or unexpected PHP files exist in the environment
The environment is affected if ThemeREX Tuning plugin is installed, contains vulnerable include/require logic using unsanitized user input, and those endpoints are accessible to attackers.
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 Tuning to the latest version; if unavailable, disable/remove the plugin and implement WAF rules to block directory traversal patterns in requests.
- 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-28032 — 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-28032 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