dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3657

HIGH · 7.5 CVSS v3.1 Published 2026-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The My Sticky Bar WordPress plugin (versions up to 2.8.6) contains a SQL injection vulnerability in the `stickymenu_contact_lead_form` AJAX action. Attackers can inject malicious SQL through POST parameter names that are used directly as column identifiers in `$wpdb->insert()` calls. While parameter values are sanitized with `esc_sql()` and `sanitize_text_field()`, the parameter keys bypass this protection and are incorporated directly into the SQL INSERT statement, enabling unauthenticated blind time-based data extraction.

MitigationUpdate My Sticky Bar plugin to version 2.8.7 or later which should properly validate parameter keys before using them in SQL queries. As a temporary workaround, disable the contact lead form functionality until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm My Sticky Bar plugin installation and version
    Locate the plugin directory (typically wp-content/plugins/my-sticky-bar/ or similar) and check the plugin header or readme.txt file for the installed version number
    Affected if The installed version is 2.8.6 or any earlier version (versions 'up to 2.8.6' are affected)
  2. Identify if contact lead form feature is active
    Access the WordPress admin dashboard and navigate to the My Sticky Bar plugin settings to determine whether the contact lead form functionality has been enabled
    Affected if The contact lead form feature is turned on in the plugin settings
  3. Verify AJAX endpoint accessibility
    Check if the WordPress AJAX handler (admin-ajax.php) responds to the 'stickymenu_contact_lead_form' action by inspecting the plugin code for registered AJAX hooks or by testing the endpoint with a probe request
    Affected if The stickymenu_contact_lead_form AJAX action is registered and accessible (unauthenticated)
  4. Confirm vulnerable code path exists
    Review the plugin source code for the stickymenu_contact_lead_form AJAX handler and verify that POST parameter keys are passed directly to $wpdb->insert() without validation on the parameter name/key
    Affected if The code uses $_POST keys as column identifiers in $wpdb->insert() calls without sanitizing the parameter names themselves

A user is affected if they have My Sticky Bar plugin version 2.8.6 or lower with the contact lead form feature enabled and the vulnerable AJAX endpoint exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update My Sticky Bar plugin to version 2.8.7 or later which should properly validate parameter keys before using them in SQL queries. As a temporary workaround, disable the contact lead form functionality until the update can be applied.

Recommended fix Moderate confidence

Version greater than 2.8.6 (check WordPress plugin repository for latest release)

  1. 1. Update the My Sticky Bar WordPress plugin to the latest available version from the WordPress plugin repository
  2. 2. If automatic updates are not enabled, navigate to Dashboard > Plugins and manually update My Sticky Bar
  3. 3. After updating, verify the plugin is functioning correctly on the site
  4. 4. Consider reviewing activity logs for any suspicious AJAX requests to stickymenu_contact_lead_form that occurred before the patch

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3657 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3657 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data