CVE-2025-2004

Simple WP Events <= 1.8.17 - Unauthenticated Arbitrary File Deletion

2025-04-07 15:52
khanhhnahk1

Strategic Overview

Status
Patched in 1.9.0
Affected Plugin
Simple WP Events
Affected Version
<= 1.8.17
CVSS
9.1Critical
Weakness type
CWE-73 · External Control of File Name or Path
CVE
CVE-2025-2004
View all Simple WP Events vulnerabilities

At a glance

CVE-2025-2004 is a critical-severity External Control of File Name or Path vulnerability in the Simple WP Events WordPress plugin, affecting versions <= 1.8.17. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.9.0; sites on affected versions should update now. Disclosed April 2025, reported by khanhhnahk1.

Vulnerability Overview

The Simple WP Events plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the wpe_delete_file AJAX action in all versions up to, and including, 1.8.17. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). CVE-2025-32509 is a duplicate of this.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-73: External Control of File Name or Path

The product allows user input to control or influence paths or file names that are used in filesystem operations.

Remediation

Update to version 1.9.0, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Simple WP Events 1.9.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C