Eleganzo <= 1.2 - Authenticated (Subscriber+) Arbitrary Directory Deletion
Strategic Overview
- Status
- Patched in 1.3
- Affected Theme
- Eleganzo
- Affected Version
<= 1.2- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-15470
At a glance
CVE-2025-15470 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Eleganzo WordPress theme, affecting versions <= 1.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.3; sites on affected versions should update now. Disclosed April 2026, reported by Phat RiO.
Vulnerability Overview
The Eleganzo theme for WordPress is vulnerable to arbitrary directory deletion due to insufficient path validation in the akd_required_plugin_callback function in all versions up to, and including, 1.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary directories on the server, including the WordPress root directory.
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 interaction from a victim user. A successful exploit has high impact on integrity.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Eleganzo <= 1.2 takes an account at Subscriber level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Eleganzo the fix is 1.3: builds <= 1.2 are affected, anything from 1.3 onward is not.
Remediation
Update to version 1.3, or a newer patched version
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. None of that substitutes for the fix: Eleganzo 1.3 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C