CVE•Published 2024-02-29•Modified 2026-04-08•1 article on news•6 live references•NVD data

CVE-2024-0590Microsoft · Clarity

Vulnerability data via NVD (ingested)

CVSS v3.1

6.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS percentile

Exploit Prediction Scoring System · top 4% of all CVEs

Weaknesses (CWE)

CWE-352Cross-Site Request Forgery (CSRF)

Description

The Microsoft Clarity plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.9.3. This is due to missing nonce validation on the edit_clarity_project_id() function. This makes it possible for unauthenticated attackers to change the project id and add malicious JavaScript via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Timeline

Published 2024-02-29

Modified 2026-04-08

External references

NVD MITRE Exploit-DB GitHub PoC trickest/cve VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag0 hosts

vuln:CVE-2024-0590

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · WP plugin path

http.html:"/wp-content/plugins/clarity/"

Matches any site loading the "clarity" plugin — doesn't rely on Shodan's vuln tag.

Shodan · product

product:"Microsoft Clarity"

All exposed Microsoft Clarity instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Clarity"

HTTP body or banner mentions "Clarity" — catches deploys Shodan didn't identify as a product.