My Site Audit <= 1.2.5 - Authenticated (Admin+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.2.5
- Affected Plugin
- My Site Audit
- Affected Version
<= 1.2.4- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24445
At a glance
CVE-2021-24445 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the My Site Audit WordPress plugin, affecting versions <= 1.2.4. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.2.5; sites on affected versions should update now. Disclosed July 2021, reported by Akash Rajendra Patil.
Vulnerability Overview
The My Site Audit WordPress plugin through 1.2.4 does not sanitise or escape the Audit Name field when creating an audit, allowing high privilege users to set JavaScript payloads in them, even when he unfiltered_html capability is disallowed, leading to an authenticated Stored Cross-Site Scripting issue.
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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in My Site Audit <= 1.2.4 takes an account at Admin level or above. 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 My Site Audit the fix is 1.2.5: builds <= 1.2.4 are affected, anything from 1.2.5 onward is not.
Remediation
Update to version 1.2.5, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: My Site Audit 1.2.5 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