CVE-2026-28006
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 Yungen yungen allows PHP Local File Inclusion.This issue affects Yungen: from n/a through <= 1.0.12.
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 Yungen WordPress theme (versions <= 1.0.12) contains a Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in PHP include/require statements. This allows attackers to include local PHP files, potentially leading to remote code execution if they can upload malicious files or access sensitive system 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.
-
Locate the ThemeREX Yungen theme installationAccess your WordPress wp-content/themes/ directory and check for a folder named 'yungen', 'trx_yungen', or similar Yungen theme variantAffected if The Yungen theme folder exists in the themes directory
-
Identify the installed theme versionOpen the theme's style.css file (typically at wp-content/themes/yungen/style.css) and look for the 'Version:' header in the comment block at the topAffected if The version listed is 1.0.12 or lower, or if no version is declared but the theme is present
-
Search for vulnerable include/require patternsExamine PHP files in the theme folder for include(), require(), include_once(), or require_once() statements that use variables or parameters without sanitization (e.g., include($_GET['file']) or include($some_user_input))Affected if Any include/require statement directly uses user-supplied input without validation
-
Check for accessible file inclusion parametersReview theme PHP files (especially in includes/ or functions/ subdirectories) to identify if $_GET, $_POST, or similar superglobals are used in file inclusion functions and are accessible via URL parametersAffected if User-controllable parameters are used in file inclusion functions and are not protected by authentication or validation
Your environment is affected if the ThemeREX Yungen theme is installed with version 1.0.12 or lower, and vulnerable file inclusion code that uses unsanitized user input exists in the theme files.
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 the Yungen theme to the latest version that addresses this vulnerability. If no patch is available, audit the theme code for insecure include/require calls and implement strict input validation using allowlists or basename() functions to prevent path traversal.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28006 — 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-28006 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