CVE-2025-47511

Welcart e-Commerce <= 2.11.13 - Authenticated (Editor+) Arbitrary File Deletion

2025-06-03 00:00
Martino Spagnuolo

Strategic Overview

Status
Patched in 2.11.14
Affected Plugin
Welcart e-Commerce
Affected Version
<= 2.11.13
CVSS
6.5Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2025-47511
View all Welcart e-Commerce vulnerabilities

At a glance

CVE-2025-47511 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Welcart e-Commerce WordPress plugin, affecting versions <= 2.11.13. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.11.14; sites on affected versions should update now. Disclosed June 2025, reported by Martino Spagnuolo.

Vulnerability Overview

The Welcart e-Commerce plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in a function in all versions up to, and including, 2.11.13. This makes it possible for authenticated attackers, with Editor-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 interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Welcart e-Commerce <= 2.11.13 takes an account at Editor 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 Welcart e-Commerce the fix is 2.11.14: builds <= 2.11.13 are affected, anything from 2.11.14 onward is not.

Remediation

Update to version 2.11.14, or a newer patched version

How does WordSec protect against this?

An attacker needs Editor 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: Welcart e-Commerce 2.11.14 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-47511https://www.wordfence.com/threat-intel/vulnerabilities/id/3f8f8319-d75f-4e71-90d4-1c60b5a8df90https://nvd.nist.gov/vuln/detail/CVE-2025-47511

Related records

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