PLUGIN SECURITY

Is Secure Custom Fields safe?

Known vulnerabilities, PHP compatibility and safer alternatives for the Secure Custom Fields WordPress plugin — checked against WP Clinic's local security database.

What this plugin does

  • Slug: secure-custom-fields

Maintenance status

Known vulnerabilities

5 known CVEs on file for Secure Custom Fields. Reported between 2026 and 2026.

CVE Vulnerability Type Severity Affected Fixed in Published Status
CVE-2026-97195 Secure Custom Fields [secure-custom-fields] < 6.9.8 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') Low 3.5 < 6.9.8 6.9.8 2026-11-08 —
CVE-2026-97194 Secure Custom Fields [secure-custom-fields] < 6.9.8 Exposure of Sensitive Information to an Unauthorized Actor Low 2.7 < 6.9.8 6.9.8 2026-11-08 —
CVE-2026-97193 Secure Custom Fields [secure-custom-fields] < 6.9.8 Authorization Bypass Through User-Controlled Key Low 2.7 < 6.9.8 6.9.8 2026-11-05 —
CVE-2026-97192 Secure Custom Fields [secure-custom-fields] < 6.9.8 Improper Access Control Low 2.7 < 6.9.8 6.9.8 2026-11-05 —
CVE-2026-92403 Secure Custom Fields [secure-custom-fields] < 6.9.4 Incorrect Authorization Unknown < 6.9.4 6.9.4 2026-09-19 —

How to fix it

Update this plugin to the latest release from wordpress.org — each CVE above lists the exact release that fixed it ("Fixed in") when one is on file.

This is the plugin's full known vulnerability history, not a scan of any specific installation — run a free scan of your own site to check your exact installed version.

Check your own WordPress site

Run a free passive scan now, or create a free account and install the WP Clinic plugin for a deep scan of your whole hosting account and AI-assisted repair.