HomeWordPress vulnerabilitiesWP Custom Cursors
WP Custom Cursors vulnerabilities
WP Custom Cursors has 4 known vulnerabilities in this database. The most recent published record is dated 9 Nov 2023.
- Known vulnerabilities
- 4
- Active installs
- 8,000+
- Latest version
- 3.3
- Last updated
- 3 Mar 2024
- Most recent
- 9 Nov 2023
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2023-32739 | Medium 4.3 | Before 3.2 | Fixed in 3.2 | 9 Nov 2023 |
| Cross-site scripting (XSS) CVE-2022-3149 | Medium 6.1 | Before 3.0.1 | Fixed in 3.0.1 | 17 Oct 2022 |
| SQL injection CVE-2022-3150 | High 7.2 | Up to 3.0 | Fixed in a later version (latest 3.3) | 17 Oct 2022 |
| Cross-site request forgery (CSRF) CVE-2022-3151 | Medium 4.3 | Before 3.0.1 | Fixed in 3.0.1 | 17 Oct 2022 |
Read the published descriptions
- CVE-2023-32739, 9 Nov 2023
- Cross-Site Request Forgery (CSRF) vulnerability in Web_Trendy WP Custom Cursors | WordPress Cursor Plugin plugin < 3.2 versions. CVE record
- CVE-2022-3149, 17 Oct 2022
- 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 CVE record
- CVE-2022-3150, 17 Oct 2022
- 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 CVE record
- CVE-2022-3151, 17 Oct 2022
- 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. CVE record
What to do if you run WP Custom Cursors
If you run WP Custom Cursors, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Custom Cursors vulnerabilities
Free. We email you when a new vulnerability is published for WP Custom Cursors, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.