# CVE-2026-97194: Secure Custom Fields WordPress plugin permission check bypass in relational fields

Source: https://junglewise.ai/threats/cve-2026-97194-the-secure-custom-fields-wordpress-plugin-before-6-9-8-does-not  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-97194 · Severity: info · Published 2026-11-08

Secure Custom Fields is a WordPress plugin that manages custom metadata for posts and content. The plugin fails to verify user permissions when displaying linked post information, allowing Contributor-level users and above to view the titles and publication status of other authors' unpublished posts that they should not have access to.

Technologies: [Secure Custom Fields](https://junglewise.ai/threats/technologies/secure-custom-fields). Vendors: [Secure Custom Fields](https://junglewise.ai/threats/vendors/secure-custom-fields).

## Quick answers

**Is CVE-2026-97194 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-97194 being exploited in the wild.

**How severe is CVE-2026-97194?** Informational severity, published 8 November 2026.

**Which products and versions are affected?** Secure Custom Fields before 6.9.8.

**Is there a fix for CVE-2026-97194?** Yes: fixed in 6.9.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-97194 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-97194?** Check whether you run Secure Custom Fields at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 6.9.8

## Technical details

The plugin lacks read-permission validation when rendering and formatting relational field values, allowing post-editing users (Contributor and above) to retrieve unpublished post titles and non-public statuses through relational field rendering. This is a missing access control check on sensitive data output. The vulnerability has been fixed in version 6.9.8.

## Affected products

- Secure Custom Fields Secure Custom Fields before 6.9.8

## Timeline

- 2026-11-05: disclosed
- 2026-11-08: patched: version 6.9.8 released

## References

- [https://wpscan.com/vulnerability/a3987e3b-fa56-4eb0-995d-e53536a336a8/](https://wpscan.com/vulnerability/a3987e3b-fa56-4eb0-995d-e53536a336a8/)

## Related threats

- [Secure Custom Fields WordPress plugin stored XSS in field definitions](https://junglewise.ai/threats/cve-2026-97195-the-secure-custom-fields-wordpress-plugin-before-6-9-8-does-not)
- [Secure Custom Fields authorization bypass in post editor](https://junglewise.ai/threats/cve-2026-97192-the-secure-custom-fields-wordpress-plugin-before-6-9-8-does-not)