WPFront Notification Bar <= 1.9.2 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.0.0
- Affected Plugin
- WPFront Notification Bar
- Affected Version
<= 1.9.2- CVSS
- 4.8Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24518
At a glance
CVE-2021-24518 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WPFront Notification Bar WordPress plugin, affecting versions <= 1.9.2. It carries a CVSS score of 4.8 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.0.0; sites on affected versions should update now. Disclosed July 2021, reported by swapnil subhash bodekar.
Vulnerability Overview
The WPFront Notification Bar WordPress plugin before 2.0.0 does not sanitise or escape its Custom CSS setting, allowing high privilege users such as admin to set XSS payload in it even when the 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.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WPFront Notification Bar <= 1.9.2 takes any authenticated account. 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 WPFront Notification Bar the fix is 2.0.0: builds <= 1.9.2 are affected, anything from 2.0.0 onward is not.
Remediation
Update to version 2.0.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WPFront Notification Bar: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPFront Notification Bar 2.0.0 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