WP Custom Cursors <= 3.0.1 - Authenticated (Administrator+) SQL Injection
Strategic Overview
- Status
- Patched in 3.0.3
- Affected Plugin
- WP Custom Cursors | WordPress Cursor Plugin
- Affected Version
<= 3.0.2- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2022-3150
At a glance
CVE-2022-3150 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Custom Cursors WordPress plugin, affecting versions <= 3.0.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 3.0.3; sites on affected versions should update now. Disclosed September 2022, reported by István Márton.
Vulnerability Overview
The WP Custom Cursors plugin for WordPress is vulnerable to SQL Injection via the ‘edit_row’ parameter and potentially others in versions up to, and including, 3.0.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. NOTE: CVE-2023-2221 appears to be a duplicate of this vulnerability.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
WP Custom Cursors <= 3.0.2 carries this weakness at edit_row, and reaching it takes an account at Administrator level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WP Custom Cursors the fix is 3.0.3: builds <= 3.0.2 are affected, anything from 3.0.3 onward is not.
Remediation
Update to version 3.0.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Custom Cursors 3.0.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Custom Cursors | WordPress Cursor Plugin
- 8.8CVE-2022-3151: WP Custom Cursors <= 3.0 CSRF to Cursor Manipulation
CVE-2022-3151 - 5.5CVE-2022-3149: WP Custom Cursors <= 3.0 Stored Cross-Site Scripting
CVE-2022-3149 - 4.4CVE-2023-5911: WP Custom Cursors | WordPress Cursor <= 3.2 Stored XSS
CVE-2023-5911 - 4.3CVE-2023-32739: WP Custom Cursors < 3.2 Cross-Site Request Forgery
CVE-2023-32739
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C