CVE-2022-3150: The WP Custom Cursors WordPress plugin before 3.2 does not properly sanitise and escape a parameter before usi

Q: How do I fix CVE-2022-3150?

wp custom cursors: upgrade to newer than 3.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-3150 being exploited?

CVE-2022-3150 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-3150 affect?

CVE-2022-3150 affects wp custom cursors. Severity is high (CVSS 7.2). The WP Custom Cursors WordPress plugin before 3.2 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privileged users such as admin

Q: How urgent is CVE-2022-3150?

Priority 47/100. High severity; Public exploit reference

This month

HIGH 7.2UPGRADE

CVE-2022-3150 is a high-severity flaw (CVSS 7.2) 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.2 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privileged users such as admin

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Published	2022-10-17
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp custom cursors project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-17 12:15 UTCPublished CVE record published
2026-06-17 04:58 UTCUpdated Record last modified

wp custom cursors project wp custom cursors UPGRADE

Affected: <= 3.0

Fixed in: newer than 3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-custom-cursors || rpm -q wp-custom-cursors || wp-custom-cursors --version

2. UPGRADE to newer than 3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-custom-cursors

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-custom-cursors

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-3150?

wp custom cursors: upgrade to newer than 3.0. Exact commands for each OS are on this page.

Is CVE-2022-3150 being exploited?

CVE-2022-3150 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-3150 affect?

CVE-2022-3150 affects wp custom cursors. Severity is high (CVSS 7.2). The WP Custom Cursors WordPress plugin before 3.2 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privileged users such as admin

How urgent is CVE-2022-3150?

Priority 47/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

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-3149 MEDIUM 6.1 UPGRADE The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when creating and editin

References

← Back to latest CVEs