Skip to main content

Modernee Theme EUVDEUVD-2025-210189

| CVE-2025-69105 HIGH
PHP Remote File Inclusion (CWE-98)
2026-06-16 Patchstack
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site running Modernee theme
  2. Delivery
    Probe vulnerable theme parameter
  3. Exploit
    Inject path traversal payload into include parameter
  4. Execution
    Server includes attacker-specified local file
  5. Persist
    Disclose wp-config.php or poisoned log
  6. Impact
    Achieve code execution as web user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Command and Control

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Target site must have the ThemeREX Modernee WordPress theme installed and active at version 1.6.0 or earlier, with the vulnerable theme endpoint network-reachable to the attacker (standard public WordPress deployment). No authentication or user interaction is required (PR:N/UI:N), but AC:H in the CVSS vector indicates the attacker must craft a specific request - likely targeting a particular theme parameter and supplying a valid local path - rather than firing a generic payload, and PHP must be configured to permit the relevant include semantics (default on most LAMP stacks). Limiting factors: sites that have already switched themes, that sit behind a WAF blocking traversal sequences, or that run with hardened open_basedir/allow_url_include=Off significantly reduce exploitability.

Impact

The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) shows a network-reachable, unauthenticated bug with high impact across all three CIA pillars, but AC:H indicates non-trivial preconditions - likely a specific request shape or knowledge of internal paths. There is no EPSS score provided, no SSVC decision available, and the vulnerability is not on the CISA KEV list, so there is no confirmed active exploitation. No public POC is referenced beyond the Patchstack advisory entry. Net effect: this is a real, high-severity LFI worth prompt remediation for any site running Modernee, but the AC:H qualifier and absence of KEV/POC data suggest it is not (yet) a mass-exploited issue, putting it below 'patch-tonight emergency' priority but firmly in 'patch this week' territory.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP request to a Modernee theme endpoint, supplying a path-traversal payload (e.g., ../../../../wp-config.php) in a parameter that flows into a PHP include statement, retrieving database credentials and secret keys. With those credentials or by chaining the LFI with log/session-file poisoning (writing PHP into a controllable file such as the access log and including it), the attacker pivots from read-only disclosure to full remote code execution under the web server user.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 17, 2026

Unauthenticated Local File Inclusion in the ThemeREX Modernee WordPress theme (versions through 1.6.0) allows remote attackers to coerce the server into including arbitrary local PHP files, enabling information disclosure and potential code execution via log poisoning or session file abuse. Reported by Patchstack and tracked as EUVD-2025-210189, no public exploit identified at time of analysis and the vulnerability is not in CISA KEV. The CVSS 8.1 score reflects high impact across confidentiality, integrity, and availability but with high attack complexity.

RemediationAI

No vendor-released patched version is independently confirmed in the available data, so administrators should monitor the ThemeREX Modernee theme changelog and the Patchstack advisory (https://patchstack.com/database/wordpress/theme/modernee/vulnerability/wordpress-modernee-theme-1-6-0-local-file-inclusion-vulnerability) for a fixed release beyond 1.6.0 and upgrade as soon as one is published. Until a patch is available, deploy a WAF rule (Patchstack vPatch, Wordfence, or equivalent) to block requests containing path traversal sequences (../, %2e%2e%2f) and PHP stream wrappers (php://, file://, data://) targeting Modernee theme endpoints; restrict PHP's open_basedir and set allow_url_include=Off and allow_url_fopen=Off in php.ini to limit traversal scope (side effect: may break legitimate plugins that rely on remote includes). As a temporary high-friction control, deactivate and switch away from the Modernee theme on production sites that handle sensitive data - accepting the visual/functional regression cost - and audit web logs for suspicious file= or template= style parameters consistent with LFI probing.

Affected VersionsENISA

Modernee n/a ≤1.6.0

Affected Packages

euvd modernee no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Modernee is a commercial WordPress theme distributed by ThemeREX (CPE cpe:2.3:a:themerex:modernee). The flaw is classified under CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program, aka 'PHP Remote File Inclusion'), meaning a PHP include/require statement uses attacker-influenced input without sufficient validation against path traversal or stream wrappers. In WordPress themes this typically manifests in template loaders, AJAX handlers, or admin-ajax endpoints that route a request parameter into include/require_once, allowing traversal sequences (../) or absolute paths to read sensitive files such as wp-config.php or to execute previously planted PHP content.

Know when Modernee gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Unauthenticated network-reachable LFI (AV:N/PR:N/UI:N); AC:H reflects required crafted request and path knowledge; full file disclosure plus log-poisoning RCE potential justifies C:H/I:H/A:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated Local File Inclusion in Modernee <= 1.6.0 versions.

Executive ViewAI

Why It Matters

The ThemeREX Modernee WordPress theme (versions 1.6.0 and earlier) contains an unauthenticated remote file inclusion vulnerability (CVSS 8.1) that allows attackers to extract sensitive files and potentially execute code without authentication. Any WordPress installation using this theme is directly exposed to information disclosure and website compromise. Immediate action is required as no vendor patch currently exists.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Deactivate and remove the Modernee theme immediately; (2) Implement WAF rules blocking common LFI payloads (e.g., patterns like '../../../etc/passwd'); (3) Apply restrictive file permissions on WordPress directories to limit information exposure; (4) Enable WordPress security logging and monitor for suspicious include/require patterns in PHP error logs; (5) Restrict theme directory access via web server configuration (.htaccess or nginx rules).

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy