CVE-2022-3149: The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when creating and editin
CVE-2022-3149 is a medium-severity flaw (CVSS 6.1) affecting wp custom cursors. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when creating and editing cursors, which could allow attackers to made a logged in admin perform such actions via CSRF attacks. Furthermore, due to the lack of sanitisation and escaping in some of the cursor options, it could also lead to Stored Cross-Site Scripting
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-3149?
wp custom cursors: upgrade to 3.0.1. Exact commands for each OS are on this page.
Is CVE-2022-3149 being exploited?
CVE-2022-3149 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-3149 affect?
CVE-2022-3149 affects wp custom cursors. Severity is medium (CVSS 6.1). The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when creating and editing cursors, which could allow attackers to made a logged in admin perform such actions via CSRF attacks. Furthermore, due to the la
How urgent is CVE-2022-3149?
Priority 32/100. Public exploit reference
Software pages
Related CVEs
- CVE-2023-2221 HIGH 7.2 UPGRADE The WP Custom Cursors WordPress plugin before 3.2 does not properly sanitise and escape a parameter before usi
- CVE-2022-3151 MEDIUM 4.3 UPGRADE The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when deleting cursors, w
- CVE-2022-3150 HIGH 7.2 UPGRADE The WP Custom Cursors WordPress plugin before 3.2 does not properly sanitise and escape a parameter before usi