Security readout for executives and security teams
Plain-English summary
CVE-2024-0590 affects the Microsoft Clarity WordPress plugin through version 0.9.3. A site administrator who is tricked into taking an action could unknowingly let an attacker change the Clarity project ID and store malicious JavaScript. This is not listed as actively exploited in the supplied sources.
Executive priority
Treat as a moderate web-risk item. Prioritize externally facing WordPress properties using Microsoft Clarity, especially sites with many administrators or weak admin security practices. The business risk is stored script execution on public pages after administrator social engineering.
Technical view
The issue is CSRF caused by missing nonce validation in edit_clarity_project_id(). The reported impact is stored cross-site scripting through a forged request that requires administrator interaction. CVSS 3.1 is 6.1, with network access, low complexity, no privileges, required user interaction, and changed scope.
Likely exposure
Exposure is limited to WordPress sites running Microsoft Clarity plugin versions up to and including 0.9.3. Sites without this plugin, or not on affected versions, are not indicated as exposed by the provided sources.
Exploitation context
The attacker must trick a WordPress administrator into performing an action such as clicking a link. The supplied bundle does not include KEV listing, confirmed exploitation, public exploit details, or broader campaign evidence.
Researcher notes
The source bundle identifies CWE-352 and a CSRF-to-stored-XSS path, but does not provide complete patch metadata beyond the WordPress Trac reference. Avoid assuming active exploitation or exact fixed version unless confirmed from vendor guidance.
Mitigation direction
- Inventory WordPress sites using the Microsoft Clarity plugin.
- Check whether installed versions are 0.9.3 or earlier.
- Review Microsoft or WordPress plugin guidance for the fixed release.
- Update or disable the plugin according to vendor guidance.
- Limit WordPress administrator access to trusted users.
Validation and detection
- Confirm plugin presence and version on each WordPress site.
- Review plugin settings for unexpected Clarity project ID changes.
- Check pages for unexpected JavaScript introduced through Clarity configuration.
- Verify the vulnerable function is protected by nonce validation after update.
- Review administrator activity around suspicious setting changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-0590 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c2f4461b-1373-4d09-8430-14d1961e1644?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3036293%40microsoft-clarity&new=3036293%40microsoft-clarity&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.