CVE-2026-28053
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 Miller christine-miller allows PHP Local File Inclusion.This issue affects Miller: from n/a through <= 1.3.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 confidenceA PHP Local File Inclusion (LFI) vulnerability in ThemeREX Miller theme (christine-miller) versions through 1.3.3 allows remote attackers to include and execute arbitrary local files via improper control of filename parameters in include/require statements. This can lead to sensitive data exposure (e.g., configuration files, credentials) and potentially remote code execution if attacker-controlled files exist on the server.
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 the installed theme and versionLocate the christine-miller theme folder in wp-content/themes/ and check the style.css file header for the Version fieldAffected if The version listed is 1.3.3 or lower
-
Verify the theme is activeCheck WordPress admin under Appearance > Themes to confirm christine-miller is activatedAffected if The theme is installed and active on the WordPress site
-
Search for vulnerable file inclusion patternsExamine PHP files in the theme directory for include/require statements that use variables from $_GET, $_POST, or $_REQUEST without proper sanitizationAffected if The theme code contains dynamic file inclusion using user-supplied input parameters
-
Inspect common LFI entry pointsReview PHP files for parameters like 'file', 'path', 'page', 'template', or 'include' that are used in include/require/require_once/require_once callsAffected if Such parameters exist and accept path values without validation
-
Check for path traversal mitigationReview the theme code to see if file inclusion functions sanitize or block '../' sequences and restrict included files to expected directoriesAffected if No such sanitization is present or it can be bypassed
A site is affected if the christine-miller theme version is 1.3.3 or lower and the theme contains file inclusion code using unsanitized user-controlled input parameters.
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 dataImplement strict input validation and whitelist-based filtering on all file inclusion parameters, use basename() to strip directory traversal sequences, and avoid user-supplied input in include/require paths entirely.
- 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-28053 — 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-28053 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