Summary
CVE-2025-69174 is a high-severity, unauthenticated Local File Inclusion (LFI) vulnerability affecting the ThemeREX Etude WordPress theme in all versions up to and including 1.6. The flaw arises from improper control of filename parameters in PHP include/require statements (CWE-98), allowing remote attackers with no credentials to force the server to include arbitrary local files. With a CVSS v3.1 base score of 8.1 (High) and full confidentiality, integrity, and availability impact, this vulnerability poses a significant risk to any internet-exposed WordPress site running the affected theme.
Technical details
-
Root cause: Improper validation of user-supplied input used in PHP
include/requirestatements (CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program), enabling an attacker to manipulate the file path passed to the inclusion function. -
Trigger conditions: No authentication or user interaction is required; the attack can be initiated directly over the network. Attack complexity is rated High, indicating that specific preconditions or configurations must be present on the target.
-
Attack vector: Remote, unauthenticated HTTP/HTTPS request to the vulnerable WordPress installation running the Etude theme.
-
Impact: An attacker can read arbitrary files from the server filesystem, including sensitive files such as
wp-config.php(containing database credentials) and system files such as/etc/passwd. In PHP environments, LFI can further escalate to Remote Code Execution (RCE) through techniques such as log poisoning, session file inclusion, or PHP filter chains.
Affected software
- ThemeREX Etude WordPress Theme, versions ≤ 1.6
Severity
-
CVSS v3.1 Base Score: 8.1 (High)
-
Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
-
No official vendor patch is currently available for CVE-2025-69174. As of the date of this publication, ThemeREX has not released a remediated version of the Etude theme.
-
Immediate workarounds:
-
If the Etude theme is not actively required, deactivate and remove it from the WordPress installation to eliminate the attack surface entirely.
-
Deploy a Web Application Firewall (WAF) or a virtual patching solution capable of blocking PHP LFI patterns.
-
Restrict access to the WordPress installation at the network level where feasible, limiting exposure to trusted IP ranges only.
-
Monitor for a vendor-issued patch and apply it immediately upon release.
-
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

