CVE-2026-97192

waiting for further signalsZero needs more public information before it can validate it.

GHSA-488p-3q24-423r ↗EUVD-2026-119461 ↗

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 < 6.9.8
fixed in 6.9.8
ETK-2026-3888Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 35msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h32m
0
+4h
+6h
+8h
+10h
+12h

description

Secure Custom Fields versions before 6.9.8 do not consistently enforce field-group location restrictions when posts are saved through the editor. An authenticated contributor or higher-privileged user can add custom fields reserved for administrators to posts they are allowed to edit.

mitigation

Upgrade Secure Custom Fields to version 6.9.8 or later. Until upgrading, restrict untrusted contributor-level accounts from editing posts where restricted custom fields could be impactful.

fixed in 6.9.8

check
no
exploit
no
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.
contextual
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
25m
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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

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
  2. 2026-11-08 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3888",
  "cve_id": "CVE-2026-97192",
  "display_id": "CVE-2026-97192",
  "ghsa_id": "GHSA-488p-3q24-423r",
  "euvd_id": "EUVD-2026-119461",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Custom-field authorization bypass in Secure Custom Fields",
  "summary": "Secure Custom Fields versions before 6.9.8 do not consistently enforce field-group location restrictions when posts are saved through the editor. An authenticated contributor or higher-privileged user can add custom fields reserved for administrators to posts they are allowed to edit.",
  "mitigation": "Upgrade Secure Custom Fields to version 6.9.8 or later. Until upgrading, restrict untrusted contributor-level accounts from editing posts where restricted custom fields could be impactful.",
  "vendor": null,
  "product": "Secure Custom Fields",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6.9.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.9.8"
      ],
      "package_name": "Secure Custom Fields",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.050717966666667,
  "t0_at": "2026-11-08T06:00:28.025000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T06:00:28.025000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T06:00:28.025000+00:00",
      "url": "https://github.com/advisories/GHSA-488p-3q24-423r"
    }
  }
}

published 2026-11-08 08:07Z
last change 2026-11-08 10:05Z

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.