Stored XSS via nonce-free project ID update
Published Feb 20, 2024 · Updated Apr 8, 2026
CSRF in Microsoft Clarity for WordPress 0.9.3 and earlier allows remote attackers to inject stored JavaScript through a forged request. The edit_clarity_project_id() function updates the stored Clarity project ID from request data without validating a WordPress nonce, allowing attacker-supplied script content to persist. Exploitation requires a logged-in site administrator to follow or submit the forged request, after which the stored script can execute in the site's origin.
Summary
What happened
CSRF in Microsoft Clarity for WordPress 0.9.3 and earlier allows remote attackers to inject stored JavaScript through a forged request. The edit_clarity_project_id() function updates the stored Clarity project ID from request data without validating a WordPress nonce, allowing attacker-supplied script content to persist. Exploitation requires a logged-in site administrator to follow or submit the forged request, after which the stored script can execute in the site's origin.
The record
- CVE
- CVE-2024-0590
- Published
- Feb 20, 2024
- Updated
- Apr 8, 2026
- Vendor
- Microsoft
- Product
- Microsoft Clarity
- Classifications
- CWE-352, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record 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=0 <=0.9.3
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
No public exploit references are available in this record.
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