CVE-2025-60217

PT Luxa Addons <= 1.2.2 - Authenticated (Subscriber+) Arbitrary File Deletion

2025-06-10 00:00
Bonds

Strategic Overview

Status
Unpatched
Affected Plugin
PT Luxa Addons
Affected Version
<= 1.2.2
CVSS
9.1Critical
Weakness type
CWE-73 · External Control of File Name or Path
CVE
CVE-2025-60217
View all PT Luxa Addons vulnerabilities

At a glance

CVE-2025-60217 is a critical-severity External Control of File Name or Path vulnerability in the PT Luxa Addons WordPress plugin, affecting versions <= 1.2.2. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2025, reported by Bonds.

Vulnerability Overview

The PT Luxa Addons plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in all versions up to, and including, 1.2.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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).

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

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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