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

High 7.5 Published Updated

Unauthenticated attackers can extract database data via SQL injection in the My Sticky Bar WordPress plugin.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-3657?

CVE-2026-3657 is a high-severity SQL injection vulnerability in premio My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu), published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-89

Which versions are affected by CVE-2026-3657?

How do I fix CVE-2026-3657?

No fix has been published for CVE-2026-3657 yet. Limit exposure of the affected software until one is available.

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2026-3657 being exploited?

There is no known exploitation of CVE-2026-3657 in the wild and no public exploit code.

Sources

Also known as GHSA-pvwh-rjjc-mwgp.

Is CVE-2026-3657 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free