LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54690: WordPress Xinterio Theme <= 4.2 - Local File Inclusion Vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A WordPress site using the Xinterio theme version 4.2 or earlier may let an unauthenticated internet user force the site to include unintended local files. The CVSS score is high, but the provided sources do not show active exploitation or a named fixed version.

Executive priority

Treat this as a high-priority WordPress exposure review for any site using Xinterio. Prioritize public websites and revenue, brand, or customer-data properties, but avoid claiming an emergency exploitation event unless new KEV or vendor evidence appears.

Technical view

CVE-2025-54690 is a CWE-98 include/require filename control flaw in themeStek Xinterio through version 4.2. The CVSS 3.1 score is 8.1 with network attack vector, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites with the themeStek Xinterio theme installed at version 4.2 or earlier. The bundle does not identify vulnerable plugin paths, hosting conditions, or whether inactive installations are exploitable.

Exploitation context

The CVE record and Patchstack entry describe local file inclusion risk, but the bundle provides no exploit details. CISA KEV status is false, so active exploitation should not be claimed from these sources.

Researcher notes

The public bundle is sparse: it confirms product, version range, CWE, CVSS, and Patchstack attribution, but not affected code paths, proof of concept, fixed release, or exploitation in the wild. Validation should focus on asset presence and vendor-confirmed remediation status.

Mitigation direction

  • Inventory WordPress sites for themeStek Xinterio and record installed versions.
  • If Xinterio is version 4.2 or earlier, check vendor or Patchstack guidance for a safe update.
  • Remove or disable Xinterio where it is not required for business operations.
  • Apply compensating controls only when backed by vendor, host, or security provider guidance.
  • Track the CVE record for updates about fixed versions or additional affected ranges.

Validation and detection

  • Confirm whether Xinterio is installed on each WordPress property.
  • Verify the installed theme version is newer than 4.2 or otherwise vendor-confirmed safe.
  • Review CVE and Patchstack records for any newly published remediation details.
  • Check asset inventories for public WordPress sites still running affected versions.
  • Review web logs for unusual requests targeting theme file inclusion behavior.
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-2025-54690 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-2025-54690Attack 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
themeStekXinterioxinterio, 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.