ZeroDay Findings
Sign inSign up

Findings

CVE-2026-3657

The My Sticky Bar plugin for WordPress is vulnerable to SQL injection via the AJAX action in all versions up to, and including, 2.8.6.

Published Mar 12, 2026 · updated Jun 17, 2026

The My Sticky Bar plugin for WordPress is vulnerable to SQL injection via the 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 . While parameter values are sanitized with and , 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.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 12, 2026 · NIST NVD

    Detected

    The My Sticky Bar plugin for WordPress is vulnerable to SQL injection via the 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 . While parameter values are sanitized with and , the parameter keys are used as-is to build the column list in the INSERT statement. This makes it possi

  2. Jun 17, 2026 · NIST NVD

    Updated

    The My Sticky Bar plugin for WordPress is vulnerable to SQL injection via the 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 . While parameter values are sanitized with and , the parameter keys are used as-is to build the column list in the INSERT statement. This makes it possi

Sources

  • CVE.orgVulnerability recordCVE-2026-3657

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-3657

    The My Sticky Bar plugin for WordPress is vulnerable to SQL injection via the 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 `$

    nvd.nist.gov

References