Files
vuln-nvd/data/2026/CVE-2026-3657.json
T

2 lines
3.5 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{"affected":[{"affectedData":[{"defaultStatus":"unaffected","product":"My Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu)","vendor":"premio","versions":[{"lessThanOrEqual":"2.8.6","status":"affected","version":"0","versionType":"semver"}]}],"source":"security@wordfence.com"}],"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."}],"id":"CVE-2026-3657","lastModified":"2026-06-17T10:43:55.690","metrics":{"cvssMetricV31":[{"cvssData":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":7.5,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"exploitabilityScore":3.9,"impactScore":3.6,"source":"security@wordfence.com","type":"Secondary"}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"id":"CVE-2026-3657","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-03-12T13:14:16.775598Z","version":"2.0.3"}}]},"published":"2026-03-12T03:15:57.923","references":[{"source":"security@wordfence.com","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"}],"sourceIdentifier":"security@wordfence.com","vulnStatus":"Deferred","weaknesses":[{"description":[{"lang":"en","value":"CWE-89"}],"source":"security@wordfence.com","type":"Secondary"}]}