← back to feed
CVE-2026-97193

CVE-2026-97193

validatingZero is analyzing and reversing it now.

GHSA-2j9h-chv5-8537 ↗EUVD-2026-119462 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Secure Custom Fields
ETK-2026-3887Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Secure Custom Fields for WordPress before 6.9.8 mishandles permission checks when synchronizing bidirectional relationships. A user with contributor access or higher may add or remove relationship references involving posts, users, or terms outside their normal editing scope when this synchronization is used.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade Secure Custom Fields to version 6.9.8 or later. Restrict contributor-level access until the update is applied.

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-08 06:00Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-2j9h-chv5-8537
  2. 2026-11-08 06:00Z

this entry in the feed

GET /api/v1/feed/CVE-2026-97193

{
  "etk_id": "ETK-2026-3887",
  "cve_id": "CVE-2026-97193",
  "display_id": "CVE-2026-97193",
  "ghsa_id": "GHSA-2j9h-chv5-8537",
  "euvd_id": "EUVD-2026-119462",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Secure Custom Fields synchronization",
  "summary": "Secure Custom Fields for WordPress before 6.9.8 mishandles permission checks when synchronizing bidirectional relationships. A user with contributor access or higher may add or remove relationship references involving posts, users, or terms outside their normal editing scope when this synchronization is used.",
  "mitigation": "Upgrade Secure Custom Fields to version 6.9.8 or later. Restrict contributor-level access until the update is applied.",
  "vendor": null,
  "product": "Secure Custom Fields",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-08T06:00:28.198000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T06:00:28.198000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T06:00:28.198000+00:00",
      "url": "https://github.com/advisories/GHSA-2j9h-chv5-8537"
    }
  }
}

published 2026-11-08 07:57Z
last change 2026-11-08 07:57Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.