A Cross-Site Scripting vulnerability in Microsoft Clarity version 0.3 can cause arbitrary code to run in a user’s browser while the browser is connected to a trusted website. The XSS payload executes whenever the user changes the clarity configuration in Microsoft Clarity version 0.3 stored on the configuring project ID page.
Securin Zero-Days
CVE-2021-33850 – Stored Cross-Site Scripting in WordPress Microsoft Clarity Plugin
Severity:Medium
Vendor
Microsoft
Affected Product
Microsoft Clarity version 0.3
CVE
CVE-2021-33850
Securin ID
2020-CSW-10-1050
Status
Fixed
Date
October 18, 2021
Description
Proof of Concept (POC):
The following vulnerability was detected in WordPress Microsoft Clarity Plugin version 0.3.
-
Log in to the WordPress application.
-
Install Microsoft Clarity plugin to your WordPress application.
Figure 1: Microsoft Clarity Plugin Installation
-
Click on Settings, and the Clarity Setting page appears.
Figure 2: Microsoft Clarity Settings Page
-
In the Clarity Settings page, enter the payload in the ‘project ID’ section (clarity_project_id parameter).
Figure 3: Entering Encoded Xss Payload in the Project ID section
-
Injected XSS payload gets executed whenever the user changes the clarity configuration page.
Figure 4: Injected XSS Payload Executed and Displays an Alert Box
Impact
An attacker can control a script executed in the victim’s browser and fully compromise the targeted user. In addition, an XSS vulnerability enables attacks that are contained within the application itself. There is no need to find an external way of inducing the victim to make a request containing their exploit. Instead, the attacker places the exploit inside the application itself and simply waits for users to encounter it, thus, resulting in the following:
-
Stealing cookies,
-
End-user files disclosure,
-
Installation of Trojan horse programs,
-
Redirection of the user to some other page or site.
Remediations
-
Perform context-sensitive encoding of untrusted input before it is echoed back to a browser by using the encoding library.
-
Implement input validation for special characters on all the variables reflected in the browser and stored in the database.
-
Implement client-side validation.
Figure 5: Cross-Site Scripting Mitigation Setting in the wp.config File Prevents Cross-site Scripting Attacks
Timeline
17 October 2021: Discovered in Microsoft Clarity version 0.3
20 October 2021: Reported to WordPress Team.
20 October 2021: WordPress acknowledged.
25 October 2021: Microsoft Clarity Plugin fixed the issue.
07 November 2021: CSW Assigned the CVE Identifier [CVE-2021-33850]