Secure Custom Fields < 6.9.8 - Contributor+ Relationship Field Update on Arbitrary Objects via IDOR
- Exploited
- No known exploitation
- Fix
- Fixed in 6.9.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.9.8.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.13% · 2nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Secure Custom Fields WordPress plugin, before the fixed release, does not check whether a user may edit a target object before changing its relationship data. A logged-in user with Contributor-level access or higher can therefore add or remove references on posts, users, or terms they are not permitted to edit.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.7/10CVSS 2.7
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 25 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.9.8.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Secure Custom Fields
fixed in 6.9.8
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-97193
Is CVE-2026-97193 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-97193?
Secure Custom Fields: before 6.9.8.Source: cve.now feed data
How do I fix CVE-2026-97193?
Upgrade to a fixed version: 6.9.8.Source: cve.now feed data