CVE-2026-97192VulnerabilityPublished 8 Nov 2026

The Secure Custom Fields WordPress plugin before 6.9.8 does not re-apply its field-group location rules when

Source GCVE Database

Compare

Authoritative record:CVE-2026-97192· Medium

Not known to be exploited : upgrade to 6.9.8 when convenient.

Data as of 8 Nov 2026, 08:04 UTC

Severity

Medium

Rated Medium 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

Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-488p-3q24-423r

What to do

Upgrade Secure Custom Fields (WordPress plugin) to 6.9.8.

Affected software

Product	Affected	Fixed in
Secure Custom Fields	Affected <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 issue is fixed. No other mitigation is indicated by the available information.

Description

The Secure Custom Fields WordPress plugin versions prior to 6.9.8 have a vulnerability where field-group location rules are not re-applied when saving values through the post editor. This flaw allows users with contributor-level access or higher to write custom fields that the site intended to restrict to administrators onto their own posts.

Impact

Users with contributor-level access or higher can write custom fields restricted to administrators on their own posts, potentially leading to unauthorized data modification or privilege escalation within the context of the affected posts. The impact is limited to the scope of posts owned by the contributor-level users.

Summary

In Secure Custom Fields WordPress plugin versions before 6.9.8, the plugin fails to re-apply its field-group location rules during the persistence of submitted values via the post editor save path. This allows users with contributor-level permissions and above to bypass restrictions and add custom fields that are normally limited to administrators on their own posts. This behavior can lead to unauthorized modification of post metadata by lower-privileged users.

References

Community reviews

Loading reviews…