{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3657 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3657 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3657 is a high-severity SQL injection vulnerability in premio My Sticky Bar – Floating Notification Bar \u0026 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."},"fix_prompt":"Check this codebase for CVE-2026-3657 and fix it if it is affected.\n\nWhat it is: CVE-2026-3657 is a high-severity SQL injection vulnerability in premio My Sticky Bar – Floating Notification Bar \u0026 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.\nExploitation: There is no known exploitation of CVE-2026-3657 in the wild and no public exploit code.\n\nAffected product: premio My Sticky Bar – Floating Notification Bar \u0026 Sticky Header (formerly myStickymenu). No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3657/ (Markdown: https://insights.sbomify.com/CVE-2026-3657/index.md)","id":"CVE-2026-3657","markdown":"https://insights.sbomify.com/CVE-2026-3657/index.md","name":"CVE-2026-3657","record":{"aliases":["GHSA-pvwh-rjjc-mwgp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract database data via SQL injection in the My Sticky Bar WordPress plugin.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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-\u003einsert()`. 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"My Sticky Bar \u003c= 2.8.6 - Unauthenticated SQL Injection via 'stickymenu_contact_lead_form' Action","id":"CVE-2026-3657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Appointment Booking Calendar \u003c= 1.6.10.0 - Unauthenticated SQL Injection via 'fields' Parameter","id":"CVE-2026-3658"},"packages":[],"prev":{"headline":"Auth bypass in OTP Login With Phone Number, OTP Verification","id":"CVE-2026-3655"},"products":["My Sticky Bar – Floating Notification Bar \u0026 Sticky Header (formerly myStickymenu)"],"published":"2026-03-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["premio"]},"summary":"Unauthenticated attackers can extract database data via SQL injection in the My Sticky Bar WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-3657/"}