Strategic Overview
- Status
- Patched in 1.0.21
- Affected Plugin
- Activity Log for WordPress
- Affected Version
< 1.0.21- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24756
At a glance
CVE-2021-24756 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Activity Log for WordPress WordPress plugin, affecting versions < 1.0.21. 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 1.0.21; sites on affected versions should update now. Disclosed November 2021, reported by wzy-ceb Attack defense.
Vulnerability Overview
The WP System Log WordPress plugin before 1.0.21 does not sanitise, validate and escape the IP address retrieved from login requests before outputting them in the admin dashboard, which could allow unauthenticated attacker to perform Cross-Site Scripting attacks against admins viewing the logs.
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')
Reaching this weakness in Activity Log for WordPress < 1.0.21 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 Activity Log for WordPress the fix is 1.0.21: builds < 1.0.21 are affected, anything from 1.0.21 onward is not.
Remediation
Update to version 1.0.21, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Activity Log for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Activity Log for WordPress 1.0.21 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C