CVE-2024-10584

DirectoryPress <= 3.6.16 - Authenticated (Author+) Stored Cross-Site Scripting

2024-12-23 00:00
Tieu Pham Trong Nhan

Strategic Overview

Status
Patched in 3.6.17
Affected Version
<= 3.6.16
CVSS
5.4Medium
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2024-10584
View all DirectoryPress – Business Directory And Classified Ad Listing vulnerabilities

At a glance

CVE-2024-10584 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the DirectoryPress WordPress plugin, affecting versions <= 3.6.16. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 3.6.17; sites on affected versions should update now. Disclosed December 2024, reported by Tieu Pham Trong Nhan.

Vulnerability Overview

The DirectoryPress – Business Directory And Classified Ad Listing plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 3.6.16 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file. When DirectoryPress Frontend is installed, this can be exploited by unauthenticated users.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in DirectoryPress <= 3.6.16 takes an account at Author level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For DirectoryPress the fix is 3.6.17: builds <= 3.6.16 are affected, anything from 3.6.17 onward is not.

Remediation

Update to version 3.6.17, or a newer patched version

How does WordSec protect against this?

An attacker needs Author 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. None of that substitutes for the fix: DirectoryPress 3.6.17 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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