LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69400: WordPress Yokoo theme <= 1.1.11 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69400 affects the WordPress Yokoo theme by ThemeREX through version 1.1.11. It can allow local file inclusion in PHP. For a public WordPress site, this may expose sensitive files or impact site integrity and availability. The available sources do not name a fixed version or confirm active exploitation.

Executive priority

Prioritize identification of public WordPress sites using Yokoo. If version 1.1.11 or earlier is found, plan prompt remediation or replacement because the potential business impact is high and no fixed version is named in the provided evidence.

Technical view

The issue is CWE-98: improper control of filenames used in PHP include/require statements. The CVSS 3.1 score is 8.1, with network access, no authentication, no user interaction, high complexity, and high confidentiality, integrity, and availability impact. Affected versions are Yokoo <= 1.1.11 according to the CVE description.

Likely exposure

Exposure is most likely on internet-facing WordPress sites using the ThemeREX Yokoo theme at version 1.1.11 or earlier. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation is rated high complexity, but requires no authentication or user interaction. Treat exposed vulnerable sites as important to triage because the impact ratings are high.

Researcher notes

Evidence is limited to CVE metadata and a Patchstack vulnerability entry. The affected-version statement is clear in the description, but the affected object is sparse and lists defaultStatus as unaffected. Validate version scope against vendor guidance before broad enforcement.

Mitigation direction

  • Inventory WordPress sites for the Yokoo theme and record installed versions.
  • If Yokoo <= 1.1.11 is present, check ThemeREX and Patchstack for current remediation guidance.
  • Update to a vendor-confirmed fixed version if one is available.
  • If no fix is available, consider removing or replacing the theme.
  • Back up the site before theme changes or updates.

Validation and detection

  • Confirm whether the active or installed theme is Yokoo.
  • Verify the Yokoo theme version from WordPress administration or asset inventory.
  • Review web logs for suspicious file access or include-related error patterns.
  • Check file integrity for unexpected theme or WordPress core modifications.
  • Monitor the CVE and Patchstack entry for fixed-version updates.
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-69400 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-69400Attack 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
ThemeREXYokooyokoo, 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.