CVE-2022-3151

WP Custom Cursors <= 3.0 - Cross-Site Request Forgery to Cursor Manipulation

2022-09-21 00:00
István Márton

Strategic Overview

Status
Patched in 3.0.1
Affected Plugin
WP Custom Cursors | WordPress Cursor Plugin
Affected Version
<= 3.0
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-3151
View all WP Custom Cursors | WordPress Cursor Plugin vulnerabilities

At a glance

CVE-2022-3151 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Custom Cursors WordPress plugin, affecting versions <= 3.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.0.1; sites on affected versions should update now. Disclosed September 2022, reported by István Márton.

Vulnerability Overview

The WP Custom Cursors plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.0. This is due to missing or incorrect nonce validation in the ~/wp-custom-cursors-add-new.php file. This makes it possible for unauthenticated attackers to manipulate cursors, via 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Custom Cursors <= 3.0 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.0.1: builds <= 3.0 are affected, anything from 3.0.1 onward is not.

Remediation

Update to version 3.0.1, 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.0.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-3151https://www.wordfence.com/threat-intel/vulnerabilities/id/112e4abe-aac7-4fac-b03f-b998374846c4https://nvd.nist.gov/vuln/detail/CVE-2022-3151

Related records

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