CVE-2021-24592

Sitewide Notice WP <= 2.2 - Authenticated Stored Cross-Site Scripting

2021-08-02 00:00
Asif Nawaz Minhas

Strategic Overview

Status
Patched in 2.3
Affected Plugin
Sitewide Notice WP
Affected Version
< 2.3
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24592
View all Sitewide Notice WP vulnerabilities

At a glance

CVE-2021-24592 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Sitewide Notice WP WordPress plugin, affecting versions < 2.3. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.3; sites on affected versions should update now. Disclosed August 2021, reported by Asif Nawaz Minhas.

Vulnerability Overview

The Sitewide Notice WP WordPress plugin before 2.3 does not sanitise some of its settings before outputting them in frontend pages, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed

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 Sitewide Notice WP < 2.3 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 Sitewide Notice WP the fix is 2.3: builds < 2.3 are affected, anything from 2.3 onward is not.

Remediation

Update to version 2.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Sitewide Notice WP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Sitewide Notice WP 2.3 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