Watcheezy Live chat plugin for WordPress <= 2.0 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.0
- Affected Plugin
- Watcheezy Live chat plugin for WordPress
- Affected Version
<= 2.0- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24305
At a glance
CVE-2021-24305 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Watcheezy Live chat plugin for WordPress WordPress plugin, affecting versions <= 2.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0; sites on affected versions should update now. Disclosed May 2021, reported by Vincent MICHEL.
Vulnerability Overview
The Target First WordPress Plugin v2.0, also previously known as Watcheezy, suffers from a critical unauthenticated stored XSS vulnerability. An attacker could change the licence key value through a POST on any URL with the 'weeWzKey' parameter that will be save as the 'weeID' option and is not sanitized.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Watcheezy Live chat plugin for WordPress <= 2.0 carries this weakness at weeWzKey, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Watcheezy Live chat plugin for WordPress the fix is 3.0: builds <= 2.0 are affected, anything from 3.0 onward is not.
Remediation
Update to version 3.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Watcheezy Live chat plugin for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Watcheezy Live chat plugin for WordPress 3.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C