LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28096: WordPress WealthCo theme <= 2.18 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28096 is a high-severity local file inclusion issue in the ThemeREX WealthCo WordPress theme through version 2.18. If exploitable, an unauthenticated remote attacker could affect confidentiality, integrity, and availability. The public sources do not show active exploitation or name a confirmed fixed version.

Executive priority

Treat as a high-priority WordPress exposure if WealthCo is used. Confirm inventory quickly, because the issue is unauthenticated and has high impact. Urgency is lower than known-exploited vulnerabilities because the provided sources do not show active exploitation.

Technical view

The CVE describes improper filename control in a PHP include/require path, classified as CWE-98. The CVSS 3.1 score is 8.1 with AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Affected product is ThemeREX WealthCo, versions through 2.18, according to the CVE and Patchstack entry.

Likely exposure

Exposure is likely limited to WordPress sites with the WealthCo theme installed at version 2.18 or earlier. The sources do not clarify whether inactive installations are exploitable, so inventory both active and installed theme copies.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation without user interaction, but with high attack complexity. The CVE is not listed as KEV in the provided data, and no cited source states active exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected range is clear, but the provided sources do not name a fixed version, workaround, proof of concept, or exploitation in the wild. Avoid assuming exploitability details beyond the CVSS vector and CWE description.

Mitigation direction

  • Inventory WordPress sites for the WealthCo theme and record installed versions.
  • Prioritize sites running WealthCo version 2.18 or earlier.
  • Check ThemeREX and Patchstack guidance for a confirmed fixed release or vendor mitigation.
  • Apply an available vendor-approved update or mitigation when confirmed.
  • Monitor web logs for suspicious file inclusion or path traversal patterns.

Validation and detection

  • Confirm whether WealthCo is installed on each WordPress site.
  • Compare installed WealthCo versions against the affected range: through 2.18.
  • Review vendor and Patchstack pages for updated remediation details.
  • Check security monitoring for anomalous requests targeting theme PHP files.
  • Document exposed sites and remediation status for vulnerability management tracking.
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-28096 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-28096Attack 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
ThemeREXWealthCowealthco, 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.