CISA list

● WordPress plugin

Secure Custom Fields

Secure Custom Fields has five security advisories. The newest release any of them names as the fix is 6.9.8.

As of , Secure Custom Fields has five security advisories. The newest release any of them names as the fix is 6.9.8.

Your version, and the version to upgrade to

Find the row your installed version falls in. The second column is the version to move to: the release an advisory names as the fix. Where the newest row ends at the last affected release and the advisories that end it call every release they do not list unaffected, it says to take any later release, or to remove the plugin if there is none. A release outside every row is one no advisory lists. That is what the advisories say, not a promise that a release is free of flaws.
If you runUpgrade toAdvisories
Before 6.9.86.9.85 advisories

Security advisories, newest first

Security advisories, newest first
AdvisoryWhat it isAffectsFixed inPublished
CVE-2026-97195Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field DefinitionLow severityBefore 6.9.86.9.8
CVE-2026-97194Secure Custom Fields < 6.9.8 - Contributor+ Unpublished Post Title and Status Disclosure via Relational FieldsLow severityBefore 6.9.86.9.8
CVE-2026-97193Secure Custom Fields < 6.9.8 - Contributor+ Relationship Field Update on Arbitrary Objects via IDORLow severityBefore 6.9.86.9.8
CVE-2026-97192Secure Custom Fields < 6.9.8 - Contributor+ Admin-Restricted Custom Field Update via Post Save PathLow severityBefore 6.9.86.9.8
CVE-2026-92403Secure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID SubstitutionLow severityBefore 6.9.46.9.4
Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use