DirectoryPress <= 3.6.19 - Cross-Site Request Forgery to Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.6.20
- Affected Version
<= 3.6.19- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-49633
At a glance
CVE-2024-49633 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the DirectoryPress WordPress plugin, affecting versions <= 3.6.19. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.6.20; sites on affected versions should update now. Disclosed January 2025, reported by Dimas Maulana.
Vulnerability Overview
The DirectoryPress – Business Directory And Classified Ad Listing plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6.19. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in DirectoryPress <= 3.6.19 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For DirectoryPress the fix is 3.6.20: builds <= 3.6.19 are affected, anything from 3.6.20 onward is not.
Remediation
Update to version 3.6.20, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to DirectoryPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: DirectoryPress 3.6.20 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in DirectoryPress – Business Directory And Classified Ad Listing
- 9.9CVE-2024-38755: DirectoryPress <= 3.6.10 SQL Injection
CVE-2024-38755 - 7.5CVE-2026-3489: DirectoryPress SQL Injection
CVE-2026-3489 - 7.3CVE-2023-37967: DirectoryPress <= 3.6.2 Missing Authorization
CVE-2023-37967 - 7.2CVE-2024-32567: DirectoryPress Reflected XSS
CVE-2024-32567 - 6.4CVE-2025-62967: DirectoryPress <= 3.6.25 Stored Cross-Site Scripting
CVE-2025-62967 - 5.4CVE-2024-10584: DirectoryPress <= 3.6.16 Stored Cross-Site Scripting
CVE-2024-10584 - 5.3CVE-2026-39566: DirectoryPress <= 3.6.26 Information Exposure
CVE-2026-39566 - 5.3CVE-2026-23548: DirectoryPress Missing Authorization
CVE-2026-23548
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C