Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 13 Mar 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Premio
Premio my Sticky Bar – Floating Notification Bar & Sticky Header (formerly Mystickymenu) Wordpress Wordpress wordpress |
|
| Vendors & Products |
Premio
Premio my Sticky Bar – Floating Notification Bar & Sticky Header (formerly Mystickymenu) Wordpress Wordpress wordpress |
Thu, 12 Mar 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 12 Mar 2026 03:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | My Sticky Bar <= 2.8.6 - Unauthenticated SQL Injection via 'stickymenu_contact_lead_form' Action | |
| Weaknesses | CWE-89 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: Wordfence
Published:
Updated: 2026-04-08T16:33:30.345Z
Reserved: 2026-03-06T18:19:56.674Z
Link: CVE-2026-3657
Updated: 2026-03-12T13:14:20.302Z
Status : Deferred
Published: 2026-03-12T03:15:57.923
Modified: 2026-04-22T21:30:26.497
Link: CVE-2026-3657
No data.
OpenCVE Enrichment
Updated: 2026-03-20T15:36:11Z