LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28032: WordPress Tuning theme <= 1.3 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28032 affects the ThemeREX Tuning WordPress theme through version 1.3. It is a local file inclusion issue that could let an unauthenticated attacker make the site include unintended server files. The published CVSS score is high, but attack complexity is rated high and no public source provided here confirms active exploitation.

Executive priority

Treat as a high-priority WordPress exposure if the Tuning theme is in use. The issue can affect confidentiality, integrity, and availability, but current sources do not show known exploitation. Focus on asset discovery, vendor guidance, and reducing exposure on public sites.

Technical view

The CVE describes improper control of a filename used in PHP include/require logic, mapped to CWE-98. Scope is WordPress ThemeREX Tuning theme versions through 1.3. CVSS 3.1 is 8.1 with network access, no privileges, no user interaction, high attack complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Tuning theme at version 1.3 or earlier. The provided data does not identify other products or plugins as affected. Internet-facing WordPress sites are the primary concern.

Exploitation context

The CVE record and Patchstack entry describe a local file inclusion vulnerability. The CVSS vector indicates remote, unauthenticated exploitation may be possible, but with high attack complexity. The source bundle states KEV is false, and no cited source confirms active exploitation.

Researcher notes

Evidence is sparse beyond the CVE metadata and Patchstack listing. The affected-version statement in the description says through <= 1.3, while the structured affected array is limited and should not be overinterpreted. Avoid assuming exploit availability, patch status, or additional affected components without vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Tuning theme and version.
  • Check ThemeREX and Patchstack guidance for a fixed version or official remediation.
  • Prioritize internet-facing sites running Tuning version 1.3 or earlier.
  • If no vendor fix is available, evaluate replacing or disabling the affected theme.
  • Ensure recent backups exist before theme changes.

Validation and detection

  • Confirm whether the Tuning theme is installed on each WordPress site.
  • Record the installed Tuning theme version and compare against <= 1.3.
  • Review vendor and Patchstack pages for updated remediation status.
  • Check whether affected sites are publicly reachable.
  • Document compensating actions for any site that cannot be remediated promptly.
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-28032 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-28032Attack 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
ThemeREXTuningtuning, 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.