CVE-2026-96963

validatedZero produced an exploit or a check.

GHSA-2mgp-38q6-99x9 ↗EUVD-2026-119467 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Pie Register <= 3.8.4.15
ETK-2026-3891Zero's internal tracking ID, independent of the CVE number., permanent identifier
+3h01mTTV
37mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+3h01magent stopped
0
+1h
+2h

description

Pie Register through version 3.8.4.15 lacks an authorization check for an AJAX action. An authenticated user with a Contributor-level role can modify invitation-code records created by an administrator.

mitigation

Update Pie Register to version 3.8.4.16 or later. Until updates are complete, restrict untrusted users from receiving the Contributor role.

check
available
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.
deterministic
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
37m
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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

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-96963

{
  "etk_id": "ETK-2026-3891",
  "cve_id": "CVE-2026-96963",
  "display_id": "CVE-2026-96963",
  "ghsa_id": "GHSA-2mgp-38q6-99x9",
  "euvd_id": "EUVD-2026-119467",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Pie Register AJAX action",
  "summary": "Pie Register through version 3.8.4.15 lacks an authorization check for an AJAX action. An authenticated user with a Contributor-level role can modify invitation-code records created by an administrator.",
  "mitigation": "Update Pie Register to version 3.8.4.16 or later. Until updates are complete, restrict untrusted users from receiving the Contributor role.",
  "vendor": null,
  "product": "Pie Register",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.8.4.15"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Pie Register",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 36.73949405,
  "t0_at": "2026-11-08T06:00:29.071000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-08T09:01:04.217424+00:00",
      "days": 0.1254067873148148,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T06:00:29.071000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-08T06:00:29.071000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T06:00:29.071000+00:00",
      "url": "https://github.com/advisories/GHSA-2mgp-38q6-99x9"
    }
  }
}

published 2026-11-08 08:24Z
last change 2026-11-08 09:26Z

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.