Secure Custom Fields vulnerabilities
Plugin slug secure-custom-fields · 5 known vulnerabilities · latest disclosed 2026-11-05 · WordPress.org page
Every listed vulnerability has a fix. Version 6.9.8 or later is not affected by any of them. If your site runs an older version, update it.
0 of 5 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Secure Custom Fields
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 4.3 | <= 6.9.7 | 6.9.8 | CVE-2026-97194 | 2026-11-05 | Advisory |
| Medium 4.3 | <= 6.9.7 | 6.9.8 | CVE-2026-97193 | 2026-11-05 | Advisory |
| Medium 4.4 | <= 6.9.7 | 6.9.8 | CVE-2026-97195 | 2026-11-05 | Advisory |
| Medium 4.3 | <= 6.9.7 | 6.9.8 | CVE-2026-97192 | 2026-11-05 | Advisory |
| Medium 5.3 | <= 6.9.3 | 6.9.4 | CVE-2026-92403 | 2026-09-17 | Advisory |
Check if a site is affected
Enter a site address to see which version of Secure Custom Fields and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Secure Custom Fields plugin safe to use?
All 5 known issues are fixed in current versions (6.9.8 or later). Keeping it updated is what matters.
How do I check which version of Secure Custom Fields my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.