CVSS 3.1
2.7 lowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NCVE-2026-97193
Low (2.7). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
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.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-639 Authorization Bypass Through User-Controlled Key
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-97193 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97193?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97193?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97193 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-97193)
HTML:
<a href="https://cve.bz/cve/CVE-2026-97193"><img src="https://cve.bz/cve/badge/CVE-2026-97193.svg" alt="CVE-2026-97193"></a>
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.