Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_clone_folder
Strategic Overview
- Status
- Patched in 2.18.17
- Affected Version
<= 2.18.16- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-0725
At a glance
CVE-2023-0725 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Wicked Folders WordPress plugin, affecting versions <= 2.18.16. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.18.17; sites on affected versions should update now. Disclosed February 2023, reported by Marco Wotschka.
Vulnerability Overview
The Wicked Folders plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.18.16. This is due to missing or incorrect nonce validation on the ajax_clone_folder function. This makes it possible for unauthenticated attackers to invoke this function via forged request granted they can trick a site administrator into performing an action such as clicking on a link leading them to perform actions intended for administrators such as changing the folder structure maintained by the plugin.
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 Wicked Folders <= 2.18.16 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 Wicked Folders the fix is 2.18.17: builds <= 2.18.16 are affected, anything from 2.18.17 onward is not.
Remediation
Update to version 2.18.17, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Wicked Folders: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Wicked Folders 2.18.17 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 5.4CVE-2023-0724: Wicked Folders <= 2.18.16 Cross-Site Request Forgery
CVE-2023-0724 - 5.4CVE-2023-0722: Wicked Folders <= 2.18.16 Cross-Site Request Forgery
CVE-2023-0722 - 5.4CVE-2023-0730: Wicked Folders <= 2.18.16 Cross-Site Request Forgery
CVE-2023-0730 - 5.4CVE-2023-0728: Wicked Folders <= 2.18.16 CSRF on ajax_save_folder
CVE-2023-0728
Other vulnerabilities in Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types
- 8.8CVE-2021-24919: Wicked Folders <= 2.18.9 Subscriber+ SQL Injection
CVE-2021-24919 - 5.4CVE-2023-0712: Wicked Folders Missing Authorization
CVE-2023-0712 - 5.4CVE-2023-0713: Wicked Folders Missing Authorization on ajax_add_folder
CVE-2023-0713 - 5.4CVE-2023-0718: Wicked Folders Missing Authorization
CVE-2023-0718 - 5.4CVE-2023-0717: Wicked Folders <= 2.18.16 Missing Authorization
CVE-2023-0717 - 5.4CVE-2023-0716: Wicked Folders Missing Authorization
CVE-2023-0716 - 5.4CVE-2023-0726: Wicked Folders <= 2.18.16 Cross-Site Request Forgery
CVE-2023-0726 - 5.4CVE-2023-0727: Wicked Folders <= 2.18.16 Cross-Site Request Forgery
CVE-2023-0727
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C