LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28065: WordPress Eject theme <= 2.17 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX Eject eject allows PHP Local File Inclusion.This issue affects Eject: from n/a through <= 2.17.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28065 is a high-severity file inclusion flaw in the WordPress Eject theme by ThemeREX, affecting versions through 2.17. A vulnerable site may allow an unauthenticated attacker to make the application include unintended local files. Public sources do not state active exploitation or a confirmed fixed version.

Executive priority

Prioritize identification this week for public WordPress sites. Escalate to urgent remediation if Eject <= 2.17 is found, especially on business-critical or externally facing sites. No active exploitation is confirmed in the provided sources, but the potential impact is high.

Technical view

The CVE describes CWE-98: improper control of filenames in PHP include/require logic, resulting in local file inclusion in ThemeREX Eject <= 2.17. CVSS 3.1 is 8.1 with network attack vector, no privileges or user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites using the ThemeREX Eject theme at version 2.17 or earlier. Internet-facing WordPress deployments are the main concern. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates remote unauthenticated exploitation is possible, but high complexity is required. The source bundle does not include proof-of-concept details, observed exploitation, or CISA KEV listing. Treat as serious because successful file inclusion can threaten sensitive data and site integrity.

Researcher notes

Public detail is sparse. The CVE and Patchstack entry identify the affected theme and vulnerability class, but the bundle does not provide vulnerable code locations, exploit conditions, indicators, or a fixed release. Avoid assuming RCE or active exploitation without additional cited evidence.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Eject theme and its installed version.
  • If Eject <= 2.17 is present, check ThemeREX and Patchstack guidance immediately.
  • If no vendor fix is available, consider replacing or disabling the theme after business review.
  • Restrict administrative access and maintain current WordPress, plugin, and theme baselines.
  • Monitor vendor advisories for a confirmed patched version or compensating controls.

Validation and detection

  • Confirm whether the Eject theme is installed on each WordPress instance.
  • Record the exact Eject theme version and compare it to <= 2.17.
  • Review web and application logs for unusual file access patterns.
  • Check whether the CVE appears in vulnerability scanners using current signatures.
  • Revalidate after any theme update, replacement, or vendor-provided mitigation.
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-28065 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-28065Attack 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
ThemeREXEjecteject, 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.