LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28081: WordPress Windsor theme <= 2.5.0 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28081 is a high-severity local file inclusion issue in the ThemeREX Windsor WordPress theme through version 2.5.0. A remote unauthenticated attacker may be able to make the site include unintended local files. The published CVSS indicates potential confidentiality, integrity, and availability impact, but exploitation requires high complexity.

Executive priority

Treat as a near-term remediation item for any public WordPress site using Windsor. The issue has high potential impact, but available sources do not show active exploitation. Prioritize asset identification, version checks, and vendor remediation tracking.

Technical view

The CVE describes improper control of a filename used in a PHP include/require statement, mapped to CWE-98. Affected product is the Windsor WordPress theme through 2.5.0. CVSS 3.1 is 8.1: network reachable, high attack complexity, no privileges, no user interaction, unchanged scope, high C/I/A impact.

Likely exposure

Exposure is likely limited to WordPress installations running ThemeREX Windsor version 2.5.0 or earlier. Sites not using the Windsor theme are not indicated as affected. The source bundle does not identify affected plugins, other ThemeREX products, or hosting platforms.

Exploitation context

The vulnerability is network-accessible and does not require authentication or user interaction per CVSS. However, attack complexity is rated high. The source bundle does not state active exploitation, and the CVE is not marked as CISA KEV.

Researcher notes

Evidence is sparse. The CVE and Patchstack entry identify Windsor through 2.5.0 and CWE-98, but the bundle does not include root-cause details, vulnerable parameters, proof-of-concept status, or a named fixed version. Do not assume exploitability beyond the published CVSS and description.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Windsor theme and record installed versions.
  • Prioritize sites running Windsor 2.5.0 or earlier for vendor guidance review.
  • Check ThemeREX, Patchstack, and WordPress administration channels for an update or official mitigation.
  • Restrict administrative access and maintain current backups while remediation is evaluated.
  • Consider disabling or replacing the theme if vendor guidance cannot be confirmed promptly.

Validation and detection

  • Confirm whether the Windsor theme is installed on each WordPress site.
  • Verify the installed Windsor version against the affected range: through 2.5.0.
  • Review web and application logs for unusual file-include related errors or requests.
  • Confirm whether an official vendor update or mitigation has been applied.
  • Document sites not using Windsor as not exposed based on current sources.
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-28081 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-28081Attack 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
ThemeREXWindsorwindsor, 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.