All 404 Redirect to Homepage < 1.21 - Reflected Cross-Site Scripting via tab Parameter
Strategic Overview
- Status
- Patched in 1.21
- Affected Plugin
- All 404 Redirect to Homepage
- Affected Version
< 1.21- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24326
At a glance
CVE-2021-24326 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the All 404 Redirect to Homepage WordPress plugin, affecting versions < 1.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.21; sites on affected versions should update now. Disclosed April 2021, reported by R3N0.
Vulnerability Overview
The tab parameter of the settings page of the All 404 Redirect to Homepage WordPress plugin before 1.21 was vulnerable to an authenticated reflected Cross-Site Scripting (XSS) issue as user input was not properly sanitised before being output in an attribute.
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 All 404 Redirect to Homepage < 1.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 All 404 Redirect to Homepage the fix is 1.21: builds < 1.21 are affected, anything from 1.21 onward is not.
Remediation
Update to version 1.21, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to All 404 Redirect to Homepage: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: All 404 Redirect to Homepage 1.21 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C