CVE-2026-3657

My Sticky Bar <= 2.8.6 - Unauthenticated SQL Injection via 'stickymenu_contact_lead_form' Action

2026-03-11 13:35
Dimas Maulana

Strategic Overview

Status
Patched in 2.8.7
Affected Plugin
My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu)
Affected Version
<= 2.8.6
CVSS
7.5High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-3657
View all My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu) vulnerabilities

At a glance

CVE-2026-3657 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the My Sticky Bar WordPress plugin, affecting versions <= 2.8.6. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.8.7; sites on affected versions should update now. Disclosed March 2026, reported by Dimas Maulana.

Vulnerability Overview

The My Sticky Bar plugin for WordPress is vulnerable to SQL injection via the `stickymenu_contact_lead_form` AJAX action in all versions up to, and including, 2.8.6. This is due to the handler using attacker-controlled POST parameter names directly as SQL column identifiers in `$wpdb->insert()`. While parameter values are sanitized with `esc_sql()` and `sanitize_text_field()`, the parameter keys are used as-is to build the column list in the INSERT statement. This makes it possible for unauthenticated attackers to inject SQL via crafted parameter names, enabling blind time-based data extraction from the database.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

My Sticky Bar <= 2.8.6 carries this weakness at insert(), and reaching it takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For My Sticky Bar the fix is 2.8.7: builds <= 2.8.6 are affected, anything from 2.8.7 onward is not.

Remediation

Update to version 2.8.7, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: My Sticky Bar 2.8.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-3657https://www.wordfence.com/threat-intel/vulnerabilities/id/05d633f5-151a-4462-a6a0-5a638d7c3404https://nvd.nist.gov/vuln/detail/CVE-2026-3657

Related records

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