LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28025: WordPress Stargaze theme <= 1.5 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28025 affects the ThemeREX Stargaze WordPress theme through version 1.5. It is a local file inclusion issue that could let an unauthenticated attacker cause serious confidentiality, integrity, and availability impact. Public data does not show CISA KEV listing or confirmed active exploitation.

Executive priority

Prioritize identification this week for internet-facing WordPress properties. Remediate or remove affected theme deployments once vendor guidance is confirmed. Escalate faster for business-critical sites because the potential impact is high even though exploitation evidence is not provided.

Technical view

The CVE describes improper control of a filename used in a PHP include/require statement, mapped to CWE-98. The CVSS 3.1 score is 8.1, with network attack vector, no privileges, no user interaction, and high attack complexity. Affected scope is Stargaze versions up to and including 1.5.

Likely exposure

Exposure is likely limited to WordPress sites running the ThemeREX Stargaze theme version 1.5 or earlier. The provided sources do not identify other affected products or plugins.

Exploitation context

The vulnerability is remotely reachable and unauthenticated per CVSS, but rated high complexity. The source bundle does not provide exploit details, public exploit confirmation, or active exploitation evidence. It is not marked as CISA KEV.

Researcher notes

Evidence is limited to the CVE entry and Patchstack database reference. The CVE title and description characterize the issue as local file inclusion, while CWE-98 terminology references PHP remote file inclusion. No patch version, exploit status, or vulnerable parameter details are included in the provided bundle.

Mitigation direction

  • Inventory WordPress sites for the Stargaze theme and installed version.
  • If Stargaze is version 1.5 or earlier, treat the site as exposed.
  • Check ThemeREX, Patchstack, or WordPress distribution channels for vendor remediation guidance.
  • If no fix is available, consider disabling or replacing the theme.
  • Prioritize backups and monitoring before making production theme changes.

Validation and detection

  • Confirm whether the active or installed theme is Stargaze.
  • Record the Stargaze version from WordPress administration or theme metadata.
  • Compare the version against the affected range: 1.5 or earlier.
  • Review vendor advisories for any fixed version or workaround.
  • Check web and application logs for unusual file access errors or theme-related anomalies.
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-28025 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-28025Attack 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
ThemeREXStargazestargaze, 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.