My Sticky Bar – Floating Notification Bar & Sticky Header (Formerly Mystickymenu)
Approved changes feed: RSS · Atom
cpe:2.3:a:premio:my_sticky_bar_–_floating_notification_bar_&_sticky_header_(formerly_mystickymenu):*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Premio (ffbffa26-97c5-5523-adc1-961519880378) |
|---|---|
| Product | My Sticky Bar – Floating Notification Bar & Sticky Header (Formerly Mystickymenu) (f070793f-afe9-5655-9dc5-373b784f053c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-3657 |
vulnerable | 2026-06-03 15:23:33.270045 |
My Sticky Bar <= 2.8.6 - Unauthenticated SQL Injection via 'stickymenu_contact_lead_form' Action
HIGH (7.5)
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.
Published: 2026-03-12T02:22:36.468Z
Updated: 2026-04-08T16:33:30.345Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-7048 |
vulnerable | 2026-06-03 14:53:59.824182 |
My Sticky Bar <= 2.6.6 - Cross-Site Request Forgery to Sensitive Information Exposure
LOW (3.1)
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.
Published: 2024-01-11T08:32:55.514Z
Updated: 2026-04-08T17:19:06.219Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.