LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28006: WordPress Yungen theme <= 1.0.12 - Local File Inclusion vulnerability

Improper 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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28006 affects the WordPress Yungen theme by ThemeREX through version 1.0.12. It can allow an unauthenticated attacker to include local files through unsafe PHP include/require handling. Successful exploitation could expose sensitive files or affect site integrity and availability. The CVSS rating is high, but exploitation complexity is listed as high.

Executive priority

Treat this as a high-priority WordPress exposure check. Prioritize internet-facing sites using Yungen, especially business-critical or customer-facing properties. Current sources do not prove active exploitation, but unauthenticated remote reachability and high potential impact justify prompt inventory and vendor-guidance review.

Technical view

The CVE describes CWE-98: improper control of filenames in PHP include/require statements, resulting in local file inclusion in the Yungen WordPress theme. CVSS 3.1 is 8.1: network-accessible, unauthenticated, no user interaction, high complexity, and high confidentiality, integrity, and availability impact. Public sources identify affected versions as through 1.0.12.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Yungen theme at version 1.0.12 or earlier. Sites not using this theme are not affected based on the provided sources. The bundle does not identify affected plugins, forks, or related products.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The vulnerability is remotely reachable and unauthenticated, but CVSS marks attack complexity as high, suggesting exploitation may depend on specific application conditions.

Researcher notes

Evidence is sparse. The public CVE and Patchstack entry identify the issue class, affected theme, version range, and CVSS vector, but do not provide a named fixed version or detailed vulnerable parameter in the supplied data. Avoid assuming exploitability beyond the stated LFI classification and CVSS metrics.

Mitigation direction

  • Identify all WordPress sites using the Yungen theme.
  • Check the installed Yungen theme version.
  • If version is 1.0.12 or earlier, review ThemeREX and Patchstack guidance.
  • Apply any vendor-provided fixed version when available.
  • If no fix is available, consider disabling or replacing the theme.
  • Restrict administrative access and maintain current WordPress hardening controls.

Validation and detection

  • Inventory WordPress themes across production, staging, and backups.
  • Confirm whether Yungen is installed or active.
  • Record the exact Yungen theme version.
  • Review web logs for suspicious file-include related requests.
  • Monitor Patchstack and CVE records for updated remediation details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28006 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-28006Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXYungenyungen, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.