WP Custom Cursors < 3.2 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.2
- Affected Plugin
- WP Custom Cursors | WordPress Cursor Plugin
- Affected Version
< 3.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-32739
At a glance
CVE-2023-32739 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Custom Cursors WordPress plugin, affecting versions < 3.2. 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.2; sites on affected versions should update now. Disclosed May 2023, reported by Kévin Mosbahi (Mika).
Vulnerability Overview
The WP Custom Cursors plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 3.2. This is due to missing or incorrect nonce validation on an unknown function. This makes it possible for unauthenticated attackers to call the function 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 WP Custom Cursors < 3.2 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 WP Custom Cursors the fix is 3.2: builds < 3.2 are affected, anything from 3.2 onward is not.
Remediation
Update to version 3.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Custom Cursors: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Custom Cursors 3.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Custom Cursors | WordPress Cursor Plugin
- 9.1CVE-2023-2221: WP Custom Cursors <= 3.1 SQL Injection
CVE-2023-2221 - 7.2CVE-2022-3150: WP Custom Cursors <= 3.0.1 SQL Injection
CVE-2022-3150 - 5.5CVE-2022-3149: WP Custom Cursors <= 3.0 Stored Cross-Site Scripting
CVE-2022-3149 - 4.4CVE-2023-5911: WP Custom Cursors | WordPress Cursor <= 3.2 Stored XSS
CVE-2023-5911
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C