Files
vuln-nvd/data/2024/CVE-2024-0590.json
T

2 lines
3.8 KiB
JSON

{"affected":[{"affectedData":[{"defaultStatus":"unaffected","product":"Microsoft Clarity","vendor":"microsoft","versions":[{"lessThanOrEqual":"0.9.3","status":"affected","version":"0","versionType":"semver"}]}],"source":"security@wordfence.com"}],"configurations":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:a:microsoft:clarity:*:*:*:*:*:wordpress:*:*","matchCriteriaId":"346875CE-CC53-4338-BA42-A49193A8561B","versionEndExcluding":"0.9.4","vulnerable":true}],"negate":false,"operator":"OR"}]}],"cveTags":[],"descriptions":[{"lang":"en","value":"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."},{"lang":"es","value":"El complemento Microsoft Clarity para WordPress es vulnerable a la Cross-Site Request Forgery en todas las versiones hasta la 0.9.3 incluida. Esto se debe a que falta la validación nonce en la función edit_clarity_project_id(). Esto hace posible que atacantes no autenticados cambien la identificación del proyecto y agreguen JavaScript malicioso a través de una solicitud falsificada, siempre que puedan engañar al administrador del sitio para que realice una acción como hacer clic en un enlace."}],"id":"CVE-2024-0590","lastModified":"2026-06-17T06:53:51.083","metrics":{"cvssMetricV31":[{"cvssData":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":6.1,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"exploitabilityScore":2.8,"impactScore":2.7,"source":"security@wordfence.com","type":"Secondary"},{"cvssData":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":6.1,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"exploitabilityScore":2.8,"impactScore":2.7,"source":"nvd@nist.gov","type":"Primary"}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"id":"CVE-2024-0590","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","timestamp":"2024-02-29T16:54:44.139578Z","version":"2.0.3"}}]},"published":"2024-02-29T01:43:22.463","references":[{"source":"security@wordfence.com","tags":["Patch"],"url":"https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3036293%40microsoft-clarity&new=3036293%40microsoft-clarity&sfp_email=&sfph_mail="},{"source":"security@wordfence.com","tags":["Third Party Advisory"],"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/c2f4461b-1373-4d09-8430-14d1961e1644?source=cve"},{"source":"af854a3a-2127-422b-91ae-364da2661108","tags":["Patch"],"url":"https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3036293%40microsoft-clarity&new=3036293%40microsoft-clarity&sfp_email=&sfph_mail="},{"source":"af854a3a-2127-422b-91ae-364da2661108","tags":["Third Party Advisory"],"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/c2f4461b-1373-4d09-8430-14d1961e1644?source=cve"}],"sourceIdentifier":"security@wordfence.com","vulnStatus":"Modified","weaknesses":[{"description":[{"lang":"en","value":"CWE-352"}],"source":"security@wordfence.com","type":"Secondary"},{"description":[{"lang":"en","value":"CWE-352"}],"source":"nvd@nist.gov","type":"Secondary"}]}