Stored XSS via forged cursor configuration
Published Oct 17, 2022 · Updated May 14, 2025
Stored XSS in WP Custom Cursors before 3.0.1 allows remote attackers to execute scripts via forged cursor configuration requests. The creation and edit handlers accept cursor_text, color, and other options without CSRF validation, sanitization, or output escaping. A logged-in administrator must visit an attacker-controlled page; the stored payload then runs when a user views or edits the cursor list.
Summary
What happened
Stored XSS in WP Custom Cursors before 3.0.1 allows remote attackers to execute scripts via forged cursor configuration requests. The creation and edit handlers accept cursor_text, color, and other options without CSRF validation, sanitization, or output escaping. A logged-in administrator must visit an attacker-controlled page; the stored payload then runs when a user views or edits the cursor list.
The record
- CVE
- CVE-2022-3149
- Published
- Oct 17, 2022
- Updated
- May 14, 2025
- Vendor
- Hamid Reza Sepehr
- Product
- WP Custom Cursors
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- May 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.1 <3.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan cursor configuration CSRF-to-XSS proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo