Secure Custom Fields vulnerabilities and CVEs

Known vulnerabilities affecting Secure Custom Fields, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.

4 vulnerabilities tracked.

— 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… CVE-2026-97195 8 Nov 2026
— 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… CVE-2026-97194 8 Nov 2026
— 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… CVE-2026-97193 8 Nov 2026
— The Secure Custom Fields WordPress plugin before 6.9.8 does not re-apply its field-group location rules when persisting values submitted… CVE-2026-97192 8 Nov 2026

What this covers

This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that Secure Custom Fields is free of vulnerabilities.

Query this from an agent over MCP · Check a lockfile by version

Other products tracked here