CVE-2026-57401

SureDash – Community, Courses & Member Dashboard <= 1.8.0 - Authenticated (SureDash User+) Arbitrary File Deletion

2026-07-08 00:00
hhhai

Strategic Overview

Status
Patched in 1.8.1
Affected Plugin
SureDash – Community, Courses & Member Dashboard
Affected Version
<= 1.8.0
CVSS
8.1High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-57401
View all SureDash – Community, Courses & Member Dashboard vulnerabilities

At a glance

CVE-2026-57401 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the SureDash WordPress plugin, affecting versions <= 1.8.0. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at SureDash User level or above. The issue is fixed in version 1.8.1; sites on affected versions should update now. Disclosed July 2026, reported by hhhai.

Vulnerability Overview

The SureDash – Community, Courses & Member Dashboard plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation a function in all versions up to, and including, 1.8.0. This makes it possible for authenticated attackers, with SureDash User-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 SureDash <= 1.8.0 takes an account at SureDash User 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 SureDash the fix is 1.8.1: builds <= 1.8.0 are affected, anything from 1.8.1 onward is not.

Remediation

Update to version 1.8.1, or a newer patched version

How does WordSec protect against this?

An attacker needs SureDash User 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: SureDash 1.8.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-57401https://www.wordfence.com/threat-intel/vulnerabilities/id/039641fe-820b-464f-a859-ba2b0ebd5844https://nvd.nist.gov/vuln/detail/CVE-2026-57401

Related records

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