CVE-2026-12574

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

GHSA-m4p5-54qh-3m78 ↗EUVD-2026-120885 ↗

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

description

DDI Central version 6200 and earlier are affected by server-side HTML/JavaScript injection in analytics PDF generation. An authenticated attacker who can influence report-template input may disclose local files.

mitigation

Apply ManageEngine's security update and move DDI Central to a release newer than 6200. Until updating, restrict access to analytics PDF generation and report-template editing to trusted accounts.

fixed in 6201

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 10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 11: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-10 11:29Z
    ghsa: trigger signal, started the run
  2. 2026-11-10 11:29Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4059",
  "cve_id": "CVE-2026-12574",
  "display_id": "CVE-2026-12574",
  "ghsa_id": "GHSA-m4p5-54qh-3m78",
  "euvd_id": "EUVD-2026-120885",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side HTML/JavaScript injection in DDI Central",
  "summary": "DDI Central version 6200 and earlier are affected by server-side HTML/JavaScript injection in analytics PDF generation. An authenticated attacker who can influence report-template input may disclose local files.",
  "mitigation": "Apply ManageEngine's security update and move DDI Central to a release newer than 6200. Until updating, restrict access to analytics PDF generation and report-template editing to trusted accounts.",
  "vendor": "Zohocorp",
  "product": "DDI Central",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6201"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6201"
      ],
      "package_name": "DDI Central",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 69.56418816666667,
  "t0_at": "2026-11-10T11:29:49.717000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T11:29:49.717000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T11:29:49.717000+00:00",
      "url": "https://github.com/advisories/GHSA-m4p5-54qh-3m78"
    }
  }
}

published 2026-11-10 14:41Z
last change 2026-11-11 00:13Z

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.