# CVE-2022-3151: WP Custom Cursors < 3.0.1 - Arbitrary Cursor Deletion via CSRF

> Attackers can force logged-in admins to delete arbitrary cursors via CSRF, requiring an upgrade to the WP Custom Cursors plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2022
- **Updated:** 14 May 2025
- **Also known as:** GHSA-vc2j-hvfp-9qwr

## What is CVE-2022-3151?

CVE-2022-3151 is a medium-severity vulnerability in Unknown WP Custom Cursors, published on 17 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when deleting cursors, which could allow attackers to made a logged in admin delete arbitrary cursors via a CSRF attack.

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

## Which versions are affected by CVE-2022-3151?

It affects 1 product.


Products: Wp Custom Cursors Project Wp Custom Cursors.

## How do I fix CVE-2022-3151?

No fix has been published for CVE-2022-3151 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3151 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3151 exists.

## Other vulnerabilities in Unknown WP Custom Cursors

- [CVE-2023-2221](https://insights.sbomify.com/CVE-2023-2221/): WP Custom Cursors < 3.2 - Admin+ SQLi (high 7.2)
- [CVE-2022-3150](https://insights.sbomify.com/CVE-2022-3150/): WP Custom Cursors < 3.2 - Admin+ SQLi (high 7.2)
- [CVE-2022-3149](https://insights.sbomify.com/CVE-2022-3149/): WP Custom Cursors < 3.0.1 - Stored Cross-Site Scripting via CSRF (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3151 and fix it if it is affected.

What it is: CVE-2022-3151 is a medium-severity vulnerability in Unknown WP Custom Cursors, published on 17 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3151 exists.

Affected product: Unknown WP Custom Cursors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3151/ (Markdown: https://insights.sbomify.com/CVE-2022-3151/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3151
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3151
- OSV: https://osv.dev/vulnerability/CVE-2022-3151

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3151/
Summaries are generated and may contain mistakes; the official description above is the record.