CVE-2026-28016
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 Luxury Wine luxury-wine allows PHP Local File Inclusion.This issue affects Luxury Wine: from n/a through <= 1.1.14.
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 (LFI) vulnerability in ThemeREX Luxury Wine WordPress theme (versions <= 1.1.14) allows attackers to include arbitrary PHP files from the server due to improper control of filenames in include/require statements.
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 the ThemeREX Luxury Wine theme filesCheck your WordPress installation's wp-content/themes/ directory for a folder named 'trx_luxury' or 'luxury-wine' or similar ThemeREX theme folderAffected if The theme folder exists in the themes directory
-
Identify the installed theme versionOpen the theme's style.css file (usually at wp-content/themes/[theme-folder]/style.css) and look for the 'Version:' declaration in the file header commentAffected if The version number listed is 1.1.14 or lower
-
Search for vulnerable include/require patternsUse grep or a file search to look for include, require, include_once, or require_once statements that use variables without sanitization - specifically patterns like 'include($_GET[...])' or 'require($somevar)' within the theme's PHP filesAffected if Any PHP files in the theme contain unsanitized file inclusion statements using request parameters
-
Verify the theme is activeIn WordPress admin, go to Appearance > Themes and check if ThemeREX Luxury Wine is the currently active themeAffected if The theme is activated on the WordPress site
-
Check for exploitation indicators in access logsReview web server access logs (Apache/nginx) for suspicious requests to theme PHP files with unusual file paths (e.g., ../../../../etc/passwd) or encoded charactersAffected if Recent access logs contain LFI attack patterns targeting the theme
You are affected if ThemeREX Luxury Wine theme version 1.1.14 or lower is installed and contains unsanitized include/require statements that use user-supplied input.
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 to a patched version of the theme; if unavailable, implement strict input validation on file inclusion parameters and avoid using user-supplied input in include/require statements.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28016 — 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-28016 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