Skip to main content
CVE-2026-97193VulnerabilityPublished

The Secure Custom Fields WordPress plugin before 6.9.8 does not verify that a user is allowed to edit the target

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-97193· High

Not known to be exploited : upgrade to 6.9.8 soon.

Data as of 8 Nov 2026, 08:05 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 WordPress plugin to version 6.9.8 or later, where this authorization check issue has been fixed. No other mitigation steps are indicated.

Description

A vulnerability in the Secure Custom Fields WordPress plugin before version 6.9.8 allows users with contributor-level access and above to modify bidirectional relationship references on posts, users, or terms they normally cannot edit. This occurs because the plugin does not verify user permissions before writing to the target object during synchronization.

References

Community reviews

Loading reviews…