WP Custom Cursors at a glance
- 6 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Oct 7, 2023.
- Ranked #2456 by popularity on WordPress.org (8,000+ active installs).
- The latest version is 3.3 (released Mar 3, 2024). The most recent security fix shipped in 3.2.
- 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your WP Custom Cursors version
Enter the WP Custom Cursors version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “WP Custom Cursors”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “WP Custom Cursors”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.3). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known WP Custom Cursors vulnerabilities
WP Custom Cursors | WordPress Cursor <= 3.2 - Authenticated (Admin+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-5911
Affected versions: ≤ 3.2
Fixed in: No fix yet
Severity: Medium 4.4 · Disclosed Oct 7, 2023
WP Custom Cursors <= 3.1 - Authenticated (Admin+) SQL Injection
SQL injection · CVE-2023-2221
Affected versions: ≤ 3.1
Fixed in: 3.2
Severity: Critical 9.1 · Disclosed May 24, 2023
WP Custom Cursors < 3.2 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2023-32739
Affected versions: < 3.2
Fixed in: 3.2
Severity: Medium 4.3 · Disclosed May 15, 2023
WP Custom Cursors <= 3.0.1 - Authenticated (Administrator+) SQL Injection
SQL injection · CVE-2022-3150
Affected versions: ≤ 3.0.2
Fixed in: 3.0.3
Severity: High 7.2 · Disclosed Sep 21, 2022
WP Custom Cursors <= 3.0 - Cross-Site Request Forgery to Cursor Manipulation
Cross-site request forgery (CSRF) · CVE-2022-3151
Affected versions: ≤ 3.0
Fixed in: 3.0.1
Severity: High 8.8 · Disclosed Sep 21, 2022
WP Custom Cursors <= 3.0 - Authenticated (Administrator+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2022-3149
Affected versions: ≤ 3.0
Fixed in: 3.0.1
Severity: Medium 5.5 · Disclosed Sep 21, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| WP Custom Cursors | WordPress Cursor <= 3.2 - Authenticated (Admin+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-5911 | ≤ 3.2 | No fix yet | Medium 4.4 | Oct 7, 2023 |
| WP Custom Cursors <= 3.1 - Authenticated (Admin+) SQL InjectionSQL injection · CVE-2023-2221 | ≤ 3.1 | 3.2 | Critical 9.1 | May 24, 2023 |
| WP Custom Cursors < 3.2 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2023-32739 | < 3.2 | 3.2 | Medium 4.3 | May 15, 2023 |
| WP Custom Cursors <= 3.0.1 - Authenticated (Administrator+) SQL InjectionSQL injection · CVE-2022-3150 | ≤ 3.0.2 | 3.0.3 | High 7.2 | Sep 21, 2022 |
| WP Custom Cursors <= 3.0 - Cross-Site Request Forgery to Cursor ManipulationCross-site request forgery (CSRF) · CVE-2022-3151 | ≤ 3.0 | 3.0.1 | High 8.8 | Sep 21, 2022 |
| WP Custom Cursors <= 3.0 - Authenticated (Administrator+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2022-3149 | ≤ 3.0 | 3.0.1 | Medium 5.5 | Sep 21, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 7, 2023.
Most common weaknesses in WP Custom Cursors
Cross-site scripting (XSS)
2 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
SQL injection
2 issues
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Cross-site request forgery (CSRF)
2 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Frequently asked questions
Is WP Custom Cursors safe to use?
WP Custom Cursors is a well-known plugin with 8,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.3) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.
How do I find which version of WP Custom Cursors my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesWP Custom Cursors on WordPress.org