SQL Injection
Affects Zohocorp DDI Central builds before 6201 that use the HA replication username handling feature. Fixed in Build 6201.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6201
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Involves the HA replication username handling feature
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Zoho Corporation's ManageEngine DDI Central has an SQL injection flaw in how it handles usernames during high-availability replication, which lets an attacker run commands as the PostgreSQL service account. The flaw can be reached remotely over the network, but the attacker must first log in with high-privilege credentials.
Read the original description
Zoho Corporation ManageEngine DDI Central version below 6201 is vulnerable to SQL injection in HA replication username handling leading to command execution as the PostgreSQL service account.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Involves the HA replication username handling featureUpgrade to a fixed version: 6201.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-12572 (SQL Injection), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-12572 (entry last updated 2026-11-10): Affected: - Zohocorp DDI Central: fixed in 6201 Fixed versions: 6201. Conditions (all must be true for the bug to be hit): - Involves the HA replication username handling feature (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/security-updates.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, high-privilege login, no user action. CISA KEV: CVE-2026-12572 is not listed as of cve.now's last read. This KEV status is for CVE-2026-12572 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.manageengine.com/dns-dhcp-ipam/security-updates/security-updates.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-12572 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-12572.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Zohocorp DDI Central
fixed in 6201
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-12572
Is CVE-2026-12572 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug is an SQL injection flaw in how DDI Central handles usernames for HA replication. The advisory says it can lead to command execution as the PostgreSQL service account.Source: manageengine.com
Which versions are affected by CVE-2026-12572?
DDI Central: before 6201.Source: cve.now feed data
Am I affected, and how do I check?
DDI Central builds from 0 up to, but not including, Build 6201 are listed as affected, and the flaw involves the HA replication username handling feature. To check a install, look at the installed build number and whether HA replication is in use.Source: manageengine.com
How do I fix CVE-2026-12572?
Upgrade DDI Central to Build 6201 or later, which is the fixed version. No workaround is listed in the facts.Source: manageengine.com