CVE-2021-24425

myStickymenu <= 2.5.1 - Authenticated Stored Cross-Site Scripting

2021-06-21 00:00
R3N0

Strategic Overview

Status
Patched in 2.5.2
Affected Version
< 2.5.2
CVSS
4.8Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24425
View all My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu) vulnerabilities

At a glance

CVE-2021-24425 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the My Sticky Bar WordPress plugin, affecting versions < 2.5.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.5.2; sites on affected versions should update now. Disclosed June 2021, reported by R3N0.

Vulnerability Overview

The Floating Notification Bar, Sticky Menu on Scroll, and Sticky Header for Any Theme – myStickymenu WordPress plugin before 2.5.2 does not sanitise or escape its Bar Text settings, allowing hight privilege users to use malicious JavaScript in it, leading to a Stored Cross-Site Scripting issue, which will be triggered in the plugin's setting, as well as all front-page of the blog (when the Welcome bar is active)

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 My Sticky Bar < 2.5.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 My Sticky Bar the fix is 2.5.2: builds < 2.5.2 are affected, anything from 2.5.2 onward is not.

Remediation

Update to version 2.5.2, or a newer patched version

How does WordSec protect against this?

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