LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69057: WordPress Eldon theme <= 1.0 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Edge-Themes Eldon eldon allows PHP Local File Inclusion.This issue affects Eldon: from n/a through <= 1.0.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69057 affects the Edge-Themes Eldon WordPress theme through version 1.0. It is a high-severity local file inclusion issue that may let an unauthenticated remote attacker cause serious confidentiality, integrity, and availability impact. Public sources do not confirm active exploitation or name a fixed version.

Executive priority

Treat this as a near-term website risk if Eldon is present. The business priority is asset identification and remediation planning, not emergency incident response unless local evidence indicates exploitation. Absence of a named patch means leadership should support rapid theme replacement if vendor guidance remains unavailable.

Technical view

The CVE describes improper control of filenames in PHP include/require logic, mapped to CWE-98. Although labeled as PHP Remote File Inclusion, the description states PHP Local File Inclusion. CVSS 3.1 is 8.1, with network access, high attack complexity, no privileges, and no user interaction.

Likely exposure

Organizations running WordPress sites with the Eldon theme installed at version 1.0 or earlier are the likely exposure group. The CVE data does not list CPEs, and the affected-version metadata is limited, so teams should validate directly in WordPress asset inventories.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation without user interaction, but with high complexity. The CVE is not listed as KEV in the provided data, and no supplied source confirms active exploitation. Public detail is limited to vulnerability classification and affected range.

Researcher notes

Evidence is sparse. The CVE and Patchstack reference agree on Eldon through 1.0 and local file inclusion. No public exploit status, fixed version, or detailed remediation is included in the provided sources. Avoid assuming other Edge-Themes products are affected.

Mitigation direction

  • Inventory WordPress sites for the Eldon theme.
  • If Eldon is unused, remove or disable it.
  • If Eldon is used, check vendor and Patchstack guidance for updates.
  • Prioritize replacement if no fixed version is available.
  • Monitor CVE and Patchstack pages for remediation updates.

Validation and detection

  • Confirm whether Eldon is installed on each WordPress site.
  • Record installed Eldon versions and flag version 1.0 or earlier.
  • Check theme files against vendor-supplied updated packages when available.
  • Review web logs for suspicious file-access patterns.
  • Document removal, replacement, or vendor-approved remediation status.
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-69057 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-69057Attack 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
Edge-ThemesEldoneldon, 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.