LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69171: WordPress Orpheus theme <= 1.3 - Local File Inclusion vulnerability

Unauthenticated Local File Inclusion in Orpheus <= 1.3 versions.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69171 is an unauthenticated local file inclusion issue in the WordPress Orpheus theme up to version 1.3. A vulnerable site could allow an attacker to make the application include local server files, potentially exposing sensitive data or disrupting the site.

Executive priority

Treat this as a high-priority WordPress exposure review. It warrants prompt inventory and remediation, especially for public websites, but the provided sources do not support calling it an active exploitation emergency.

Technical view

The vulnerability is classified as CWE-98 in ThemeREX Orpheus for WordPress, reported as affecting versions <= 1.3. CVSS 3.1 is 8.1 high: network reachable, unauthenticated, no user interaction, high complexity, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on public WordPress sites with the Orpheus theme installed at version 1.3 or earlier. The source bundle does not prove exposure for other ThemeREX products, plugins, or WordPress themes.

Exploitation context

The CVE bundle marks KEV as false, and the provided sources do not state active exploitation. The issue is unauthenticated and network reachable, but CVSS lists attack complexity as high. No exploit details or proof-of-concept are included in the provided evidence.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack VDB reference. The bundle does not provide vulnerable parameters, exploit conditions, affected code paths, or a confirmed fixed version. Do not broaden affected scope beyond Orpheus <= 1.3.

Mitigation direction

  • Inventory WordPress sites for the Orpheus theme and exact installed version.
  • Remove, disable, or replace Orpheus if version is 1.3 or earlier.
  • Check ThemeREX and Patchstack guidance for a fixed release or vendor mitigation.
  • Prioritize public-facing and business-critical WordPress properties first.

Validation and detection

  • Confirm whether Orpheus is installed, active, or present but unused on each WordPress site.
  • Record the theme version and compare it with the <= 1.3 affected range.
  • Review application and web logs for unusual file inclusion or theme-path requests.
  • Verify remediation by confirming the vulnerable theme version is no longer present.
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-69171 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
3Timeline 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.9Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2025-69171Attack 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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXOrpheusorpheus, n/aunaffected
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.