CVE-2023-5509

myStickymenu <= 2.6.4 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Form Lead Deletion

2023-10-27 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 2.6.5
Affected Plugin
My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu)
Affected Version
<= 2.6.4
CVSS
6.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-5509
View all My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu) vulnerabilities

At a glance

CVE-2023-5509 is a medium-severity Missing Authorization vulnerability in the My Sticky Bar WordPress plugin, affecting versions <= 2.6.4. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.6.5; sites on affected versions should update now. Disclosed October 2023, reported by Krzysztof Zając.

Vulnerability Overview

The Floating Notification Bar, Sticky Menu on Scroll, Announcement Banner, and Sticky Header for Any Theme – My Sticky Bar (formerly myStickymenu) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the my_sticky_menu_bulks() function in all versions up to, and including, 2.6.4. This makes it possible for authenticated attackers, with subscruber-level access and above, to delete arbitrary form leads. There were several additional AJAX actions in the plugin with missing capability checks as well such as mystickymenu_admin_send_message_to_owner(), stickymenu_widget_delete(), mystickymenu_widget_status() and more that make is possible for authenticated attackers to perform unauthorized actions.

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-862: Missing Authorization

My Sticky Bar <= 2.6.4 carries this weakness at my_sticky_menu_bulks(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For My Sticky Bar the fix is 2.6.5: builds <= 2.6.4 are affected, anything from 2.6.5 onward is not.

Remediation

Update to version 2.6.5, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: My Sticky Bar 2.6.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-5509https://www.wordfence.com/threat-intel/vulnerabilities/id/102bab51-2dc7-4013-8273-21e2ff6cdf79https://nvd.nist.gov/vuln/detail/CVE-2023-5509

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C