HomeWordPress vulnerabilitiesSecure Custom Fields
Secure Custom Fields vulnerabilities
Secure Custom Fields has 6 known vulnerabilities in this database. The most recent published record is dated 8 Nov 2026.
- Known vulnerabilities
- 6
- Active installs
- 100,000+
- Latest version
- 6.9.8
- Last updated
- 3 Nov 2026
- Most recent
- 8 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-97192 | Low 2.7 | Before 6.9.8 | Fixed in 6.9.8 | 8 Nov 2026 |
| Broken access control CVE-2026-97193 | Low 2.7 | Before 6.9.8 | Fixed in 6.9.8 | 8 Nov 2026 |
| Sensitive data exposure CVE-2026-97194 | Low 2.7 | Before 6.9.8 | Fixed in 6.9.8 | 8 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-97195 | Low 3.5 | Before 6.9.8 | Fixed in 6.9.8 | 8 Nov 2026 |
| Broken access control CVE-2026-92403 | Low 3.7 | Before 6.9.4 | Fixed in 6.9.4 | 19 Sep 2026 |
| Security weakness CVE-2024-9529 | Medium 6.6 | Before 6.3.9 | Fixed in 6.3.9 | 15 Nov 2024 |
Read the published descriptions
- CVE-2026-97192, 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 through the post editor save path, allowing users with contributor-level access and above to write custom fields the site restricted to administrators onto their own posts. CVE record
- CVE-2026-97193, 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 it during bidirectional relationship synchronization, allowing users with contributor-level access and above to add or remove a reference to their own object on arbitrary posts, users, or terms they cannot otherwise edit. CVE record
- CVE-2026-97194, 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 its relational fields, allowing users with post-editing access (Contributor and above) to disclose the titles and non-public statuses of other users' unpublished posts. CVE record
- CVE-2026-97195, 8 Nov 2026
- 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 attribute name, allowing a user able to configure its fields to store a payload that executes as JavaScript in the browser of any user who views a page rendering the affected field, which on multisite lets a site administrator who lacks the unfiltered_html capability inject script into other users' sessions. CVE record
- CVE-2026-92403, 19 Sep 2026
- The Secure Custom Fields WordPress plugin before 6.9.4 does not properly verify that a front-end form submission corresponds to the form that was rendered to the visitor, allowing unauthenticated users to submit against a different registered form and modify the title and content of the post that form is bound to. CVE record
- CVE-2024-9529, 15 Nov 2024
- The Secure Custom Fields WordPress plugin before 6.3.9, Secure Custom Fields WordPress plugin before 6.3.6.3, Advanced Custom Fields Pro WordPress plugin before 6.3.9 does not prevent users from running arbitrary functions through its setting import functionalities, which could allow high privilege users such as admin to run arbitrary PHP functions. CVE record
What to do if you run Secure Custom Fields
If you run Secure Custom Fields, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Secure Custom Fields vulnerabilities
Free. We email you when a new vulnerability is published for Secure Custom Fields, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.