CVE-2026-97195: fallo de gravedad baja en Secure Custom Fields
Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition
Publicada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
28Vexday Risk Score
Sin señal de explotación. Ella tiene prueba de concepto pública.
ssvc Attendcvss 3.5epss 0.1%
The Secure Custom Fields WordPress plugin before 6.9.8 does not sanitize a persisted field definition before emitting part of it as an HTML attribute name, allowing a user able to configure its fields to store a payload that executes as JavaScript in the browser of any user who views a page rendering the affected field, which on multisite lets a site administrator who lacks the unfiltered_html capability inject script into other users' sessions.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
Productos afectados
Unknown · Secure Custom FieldsPoCs públicas encontradas — 1
cve_referencewpscan.com/vulnerability/a2fb296c-e7f4-4a40-b503-aa709c7b88bb/no verificado⚠ Recursos públicos, para evaluar la exposición de sistemas que controlas o estás autorizado a probar. Prueba solo con autorización.
CVEs relacionadas — Secure Custom Fields
En el mismo producto, de las más peligrosas a las menos.
CVE-2024-9529MEDIUMSecure Custom Fields < 6.3.6.3 - Admin+ Remote Code ExecutionEPSS 0.4%CVE-2026-92403LOWSecure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID SubstitutionEPSS 0.3%CVE-2026-97194LOWSecure Custom Fields < 6.9.8 - Contributor+ Unpublished Post Title and Status Disclosure via Relational FieldsEPSS 0.2%CVE-2026-97193LOWSecure Custom Fields < 6.9.8 - Contributor+ Relationship Field Update on Arbitrary Objects via IDOREPSS 0.2%CVE-2026-97192LOWSecure Custom Fields < 6.9.8 - Contributor+ Admin-Restricted Custom Field Update via Post Save PathEPSS 0.2%