Skip to main content
VulnerabilityPublished

CVE-2026-97193: Secure Custom Fields (WordPress plugin) · Insecure Direct Object Reference

Affects Secure Custom Fields (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to 6.9.8 soon.

Data as of 8 Nov 2026, 07:03 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 6.9.8

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade Secure Custom Fields (WordPress plugin) to 6.9.8.

Affected software

ProductAffectedFixed in
Secure Custom FieldsAffected
  • <6.9.8
Fixed in
  • 6.9.8

AI-suggested

Upgrade the Secure Custom Fields plugin to version 6.9.8 or later, where this authorization bypass vulnerability is fixed. No additional mitigation steps are required once the plugin is updated.

Description

The Secure Custom Fields WordPress plugin before version 6.9.8 contains an authorization bypass vulnerability. This flaw allows users with contributor-level access or higher to modify bidirectional relationship references on posts, users, or terms they are not authorized to edit. The issue arises because the plugin does not verify user permissions before synchronizing these relationships.

References

Community reviews

Loading reviews…