LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69068: WordPress Muji theme <= 1.2.0 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69068 is a high-severity local file inclusion issue in the WordPress Muji theme by AncoraThemes, affecting versions through 1.2.0. A vulnerable site could allow an unauthenticated remote attacker to include local files, with potential confidentiality, integrity, and availability impact. The source bundle does not show known active exploitation.

Executive priority

Treat this as a high-priority WordPress exposure review. Prioritize public websites using the Muji theme, especially business-critical or high-traffic properties. If no fixed version is available, risk-reduction may require disabling or replacing the theme.

Technical view

The CVE describes improper control of filenames in PHP include/require behavior, mapped to CWE-98. CVSS 3.1 is 8.1: network-accessible, unauthenticated, no user interaction, high complexity, and high C/I/A impact. Affected product is Muji WordPress theme through version 1.2.0.

Likely exposure

Exposure is limited to WordPress sites with the AncoraThemes Muji theme installed at version 1.2.0 or earlier. Internet-facing WordPress deployments are the primary concern. The sources do not identify affected plugins, other themes, or a fixed version.

Exploitation context

The CVE is not listed as CISA KEV in the provided data, and no cited source states active exploitation. The vector is remote and unauthenticated, but the CVSS vector marks attack complexity as high.

Researcher notes

The source bundle contains a version-range statement through 1.2.0, CVSS 8.1, CWE-98, and a Patchstack reference. It does not provide exploit details, proof of active exploitation, or a named patched version. The affected metadata is sparse and should be verified against vendor/Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the Muji theme and its installed version.
  • If Muji is at or below 1.2.0, check vendor or Patchstack guidance immediately.
  • Update to a fixed release if one is available from trusted sources.
  • If no fix is available, consider disabling or replacing the theme.
  • Restrict administrative access and monitor WordPress file integrity.

Validation and detection

  • Confirm whether the Muji theme is installed on each WordPress site.
  • Record the exact theme version and compare it with the affected range.
  • Review vendor, CVE, and Patchstack pages for updated remediation details.
  • Check logs for unusual file access or PHP include-related errors.
  • Verify backups and recovery procedures for affected WordPress sites.
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-69068 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-69068Attack 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
AncoraThemesMujimuji, 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.