Read the docs

Secure Custom Fields lets contributors modify arbitrary objects

Priority LOW 13CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-639.

Summary

The Secure Custom Fields WordPress plugin before 6.9.8 does not check whether a user may edit the target object during bidirectional relationship synchronization (CWE-639). Users with contributor-level access and above can add or remove a reference to their own object on arbitrary posts, users, or terms they cannot otherwise edit. A public exploit is linked in the references.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00168 6th percentileScored 2026-11-16
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed Secure Custom Fields (Unknown): 6.9.8

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownSecure Custom Fieldsbefore 6.9.86.9.8Patch availableCNA
  • Secure Custom Fields VendorUnknown Affected before 6.9.8 Fixed in 6.9.8 Patch available CNA

Remediation

Update Secure Custom Fields to version 6.9.8, the fixed version.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

  • Fix · CNA Secure Custom Fields (Unknown) Fixed in 6.9.8

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Secure Custom Fields 6.9.8

    4 records Highest priority Priority LOW 4 LOW

    Other records, highest priority first

    • TI-2026-86767 Stored cross-site scripting in Secure Custom Fields pluginPriority LOW 16
    • TI-2026-86766 Secure Custom Fields leaks unpublished post titles and statusesPriority LOW 13
    • TI-2026-86764 Improper access control in Secure Custom Fields WordPress pluginPriority LOW 13

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-97193
  2. 2026-11-08 Alias added: GHSA-2j9h-chv5-8537
  3. 2026-11-08 CVSS score added · CISA ADP
  4. 2026-11-08 Weakness changed · CISA ADP
  5. 2026-11-08 CISA SSVC decision points changed

References

Sources