CVE-2023-7048

My Sticky Bar <= 2.6.6 - Cross-Site Request Forgery to Sensitive Information Exposure

2024-01-03 00:00
Ulyses Saicha

Strategic Overview

Status
Patched in 2.6.7
Affected Version
<= 2.6.6
CVSS
3.1Low
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-7048
View all My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu) vulnerabilities

At a glance

CVE-2023-7048 is a low-severity Cross-Site Request Forgery (CSRF) vulnerability in the My Sticky Bar WordPress plugin, affecting versions <= 2.6.6. It carries a CVSS score of 3.1 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 2.6.7; sites on affected versions should update now. Disclosed January 2024, reported by Ulyses Saicha.

Vulnerability Overview

The My Sticky Bar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.6.6. This is due to missing or incorrect nonce validation in mystickymenu-contact-leads.php. This makes it possible for unauthenticated attackers to trigger the export of a CSV file containing contact leads via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Because the CSV file is exported to a public location, it can be downloaded during a very short window of time before it is automatically deleted by the export function.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in My Sticky Bar <= 2.6.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For My Sticky Bar the fix is 2.6.7: builds <= 2.6.6 are affected, anything from 2.6.7 onward is not.

Remediation

Update to version 2.6.7, 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.6.7 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