WPFront Notification Bar <= 3.5.1 - Reflected Cross-Site Scripting via REQUEST_URI
Strategic Overview
- Status
- Patched in 3.5.2
- Affected Plugin
- WPFront Notification Bar
- Affected Version
<= 3.5.1- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-93896
At a glance
CVE-2026-93896 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 <= 3.5.1. 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.5.2; sites on affected versions should update now. Disclosed October 2026, reported by Nabil Irawan.
Vulnerability Overview
The WPFront Notification Bar plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 3.5.1. This is due to the debug-log output path (write_debug_logs) reflecting the raw value of $_SERVER['REQUEST_URI'] through vprintf() directly inside a <script> block emitted on wp_footer, without any sanitization or escaping (see the 'Current URL is "%s"' log entry produced by the URL-text display filter in the filter() method). This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a specially crafted link.
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')
WPFront Notification Bar <= 3.5.1 carries this weakness at REQUEST_URI, 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 WPFront Notification Bar the fix is 3.5.2: builds <= 3.5.1 are affected, anything from 3.5.2 onward is not.
Remediation
Update to version 3.5.2, 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 3.5.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2024-29819: WPFront Notification Bar <= 3.3.2 Stored XSS
CVE-2024-29819 - 5.4CVE-2021-24601: WPFront Notification Bar <= 2.0.0 Stored XSS
CVE-2021-24601 - 4.8CVE-2021-24518: WPFront Notification Bar <= 1.9.2 Stored XSS
CVE-2021-24518 - 4.4CVE-2024-0625: WPFront Notification Bar <= 3.3.2 Stored XSS
CVE-2024-0625
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C