LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69038: WordPress Hyori theme <= 1.3.6 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69038 affects the WordPress Hyori theme through version 1.3.6. It may let an unauthenticated remote attacker include local files through unsafe PHP include/require handling. Impact is rated high because confidentiality, integrity, and availability could all be affected. No provided source confirms active exploitation.

Executive priority

Prioritize internet-facing WordPress sites using Hyori. Treat as a high-severity exposure, but avoid emergency assumptions unless your environment confirms the theme is installed or new sources confirm exploitation. If Hyori is not used, business risk from this CVE is likely minimal.

Technical view

The issue is classified as CWE-98: improper control of filename in PHP include/require. 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. Public detail is limited to the CVE and Patchstack entry; no exploit procedure or confirmed fixed version is included in the provided sources.

Likely exposure

Exposure is limited to WordPress sites using the goalthemes Hyori theme at version 1.3.6 or earlier. Sites not using Hyori are not indicated as affected. Internet-facing WordPress sites have higher practical urgency because the vector is network-accessible and requires no authentication.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation with high attack complexity and no user interaction. The provided data does not show CISA KEV listing, active exploitation, public exploit availability, or exploitation prerequisites beyond the vulnerable theme condition.

Researcher notes

The CVE record names Hyori through 1.3.6 and provides CVSS 8.1. The affected data in the bundle is sparse and does not identify a patched version. Validate against authoritative vendor and Patchstack updates before closing remediation tickets. Do not infer active exploitation from severity alone.

Mitigation direction

  • Inventory WordPress sites for the Hyori theme and its installed version.
  • Check goalthemes, WordPress marketplace, and Patchstack guidance for a fixed release or workaround.
  • Update Hyori if a vendor-supported fixed version is available.
  • Remove or disable Hyori where it is unused or business-nonessential.
  • Monitor affected sites for unexpected file changes and suspicious PHP errors.

Validation and detection

  • Confirm whether Hyori is installed on each WordPress site.
  • Record the Hyori version and compare it to <= 1.3.6.
  • Review web and application logs for suspicious file path requests.
  • Check for unexpected changes in theme, plugin, upload, and configuration files.
  • Document remediation status and remaining sites awaiting vendor guidance.
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-69038 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-69038Attack 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
goalthemesHyorihyori, 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.