# CVE-2023-32739: WordPress WP Custom Cursors Plugin < 3.2 is vulnerable to Cross Site Request Forgery (CSRF)


- **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
- **Fix available:** No
- **Published:** 9 Nov 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-q4v4-5ph9-rrcc

## What is CVE-2023-32739?

CVE-2023-32739 is a medium-severity vulnerability in Web_Trendy WP Custom Cursors | WordPress Cursor Plugin, published on 9 Nov 2023. 

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in Web_Trendy WP Custom Cursors | WordPress Cursor Plugin plugin < 3.2 versions.

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

## Which versions are affected by CVE-2023-32739?

It affects 1 product.


Products: Hamidrezasepehr Custom Cursors.

## How do I fix CVE-2023-32739?

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

## Is CVE-2023-32739 being exploited?

There is no known exploitation of CVE-2023-32739 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32739 and fix it if it is affected.

What it is: CVE-2023-32739 is a medium-severity vulnerability in Web_Trendy WP Custom Cursors | WordPress Cursor Plugin, published on 9 Nov 2023. 
Exploitation: There is no known exploitation of CVE-2023-32739 in the wild and no public exploit code.

Affected product: Web_Trendy WP Custom Cursors | WordPress Cursor Plugin. 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-2023-32739/ (Markdown: https://insights.sbomify.com/CVE-2023-32739/index.md)
```

## Sources

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

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