Secure Custom Fields
secure-custom-fields · plugin
Known security vulnerabilities for Secure Custom Fields. Find out in seconds which version runs on your site with WP Lens.
1 known vulnerabilities
1 exploitable without logging in · latest Sep 19, 2026
Before you install
Use with care
- 1 record needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 6.9.7 · last updated Oct 21, 2026 · 100K+ installs
wordpress.org status checked on Oct 31, 2026
Vulnerabilities
- Low 3.7
CVE-2026-92403unauthenticated→ 6.9.4
Secure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID Substitution
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).