Unknown Secure Custom Fields vulnerabilities
5 CVEs affecting Unknown Secure Custom Fields, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-97195, published 2026-11-08.
More from Unknown.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2026-92403, published 2026-09-19. Low severity, CVSS 3.7. EPSS: 0.3% probability of exploitation activity in the next 30 days. The Secure Custom Fields WordPress plugin before 6.9.4 does not properly verify that a front-end form submission corresponds to the form that was rendered to the visitor, allowing unauthenticated…
- CVE-2026-97194, published 2026-11-08. Low severity, CVSS 2.7. EPSS: 0.2% probability of exploitation activity in the next 30 days. The Secure Custom Fields WordPress plugin before 6.9.8 does not perform a read-permission check when it renders and formats the values of its relational fields, allowing users with post-editing…
- CVE-2026-97193, published 2026-11-08. Low severity, CVSS 2.7. EPSS: 0.2% probability of exploitation activity in the next 30 days. The Secure Custom Fields WordPress plugin before 6.9.8 does not verify that a user is allowed to edit the target object before writing to it during bidirectional relationship synchronization,…
- CVE-2026-97192, published 2026-11-08. Low severity, CVSS 2.7. EPSS: 0.2% probability of exploitation activity in the next 30 days. The Secure Custom Fields WordPress plugin before 6.9.8 does not re-apply its field-group location rules when persisting values submitted through the post editor save path, allowing users with…
- CVE-2026-97195, published 2026-11-08. Low severity, CVSS 3.5. EPSS: 0.1% probability of exploitation activity in the next 30 days. 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…