CVE-2026-76981

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

GHSA-7hq5-2jh9-qmh8 ↗EUVD-2026-123274 ↗

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

description

ADAudit Plus versions earlier than build 8711 are affected by a second-order SQL injection flaw in the custom reports module. An authenticated attacker may be able to manipulate database queries through that module; access to an authenticated account is required.

mitigation

Upgrade ADAudit Plus to build 8711 or later. Until the upgrade is complete, restrict access to the custom reports module to trusted authenticated users.

fixed in 8711

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 07:29Z
Δ 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-11 07:29Z
    ghsa: trigger signal, started the run
  2. 2026-11-11 07:29Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4156",
  "cve_id": "CVE-2026-76981",
  "display_id": "CVE-2026-76981",
  "ghsa_id": "GHSA-7hq5-2jh9-qmh8",
  "euvd_id": "EUVD-2026-123274",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Second-order SQL injection in ADAudit Plus custom reports",
  "summary": "ADAudit Plus versions earlier than build 8711 are affected by a second-order SQL injection flaw in the custom reports module. An authenticated attacker may be able to manipulate database queries through that module; access to an authenticated account is required.",
  "mitigation": "Upgrade ADAudit Plus to build 8711 or later. Until the upgrade is complete, restrict access to the custom reports module to trusted authenticated users.",
  "vendor": "Zohocorp",
  "product": "ADAudit Plus",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 8711"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "8711"
      ],
      "package_name": "ADAudit Plus",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 74.8156692,
  "t0_at": "2026-11-11T07:29:50.300000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T07:29:50.300000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T07:29:50.300000+00:00",
      "url": "https://github.com/advisories/GHSA-7hq5-2jh9-qmh8"
    }
  }
}

published 2026-11-11 10:41Z
last change 2026-11-11 12:45Z

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.