{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-20T08:09:49.817","vulnerabilities":[{"cve":{"id":"CVE-2026-3657","sourceIdentifier":"security@wordfence.com","published":"2026-03-12T03:15:57.923","lastModified":"2026-03-12T21:07:53.427","vulnStatus":"Awaiting Analysis","cveTags":[],"descriptions":[{"lang":"en","value":"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."},{"lang":"es","value":"El plugin My Sticky Bar para WordPress es vulnerable a inyección SQL a través de la acción AJAX 'stickymenu_contact_lead_form' en todas las versiones hasta la 2.8.6, inclusive. Esto se debe a que el gestor utiliza nombres de parámetros POST controlados por el atacante directamente como identificadores de columna SQL en '$wpdb->insert()'. Si bien los valores de los parámetros se sanean con 'esc_sql()' y 'sanitize_text_field()', las claves de los parámetros se utilizan tal cual para construir la lista de columnas en la sentencia INSERT. Esto hace posible que atacantes no autenticados inyecten SQL a través de nombres de parámetros manipulados, lo que permite la extracción ciega de datos basada en tiempo de la base de datos."}],"metrics":{"cvssMetricV31":[{"source":"security@wordfence.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE"},"exploitabilityScore":3.9,"impactScore":3.6}]},"weaknesses":[{"source":"security@wordfence.com","type":"Secondary","description":[{"lang":"en","value":"CWE-89"}]}],"references":[{"url":"https://plugins.trac.wordpress.org/browser/mystickymenu/tags/2.8.6/mystickymenu.php#L2001","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/mystickymenu/tags/2.8.6/mystickymenu.php#L2386","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/mystickymenu/tags/2.8.6/mystickymenu.php#L2396","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/mystickymenu/trunk/mystickymenu.php#L2386","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/changeset?old_path=/mystickymenu/tags/2.8.6&new_path=/mystickymenu/tags/2.8.7","source":"security@wordfence.com"},{"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/05d633f5-151a-4462-a6a0-5a638d7c3404?source=cve","source":"security@wordfence.com"}]}}]}