CVE
Authenticated Injection
Only affects Zohocorp DDI Central 6.3.0 (Build 6300) when it manages Windows DNS servers. Fixed in Build 6301.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6301
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. DDI Central is managing Windows DNS servers (Windows-backed DNS zones). Affected DDI Central version is 6.3.0 / Build 6300.
- Published
- 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? →
- 17/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
Zohocorp ManageEngine DDI Central has a PowerShell injection flaw in how it handles user-supplied TXT record values during Windows DNS operations. An attacker who can log in with a low-privilege account can reach it remotely over the network and run commands with the same access as the application.
Read the original description
Zohocorp ManageEngine DDI Central versions below 6301 is affected by a PowerShell injection vulnerability due to insufficient validation of user-supplied TXT record values in Windows DNS operations.
Who should check
Teams running ManageEngine DDI Central 6.3.0 (Build 6300) that manage Windows DNS servers and grant DNS zone management permissions.
Read the source excerpt
“Affected Software Version(s): DDI Central 6.3.0 / Build 6300”
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
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
DDI Central is managing Windows DNS servers (Windows-backed DNS zones). Affected DDI Central version is 6.3.0 / Build 6300.Upgrade to a fixed version: 6301.
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-19421 (Authenticated 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-19421 (entry last updated 2026-11-12):
Affected:
- Zohocorp DDI Central: fixed in 6301
Fixed versions: 6301.
Conditions (all must be true for the bug to be hit):
- DDI Central is managing Windows DNS servers (Windows-backed DNS zones). (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19421.html)
- Affected DDI Central version is 6.3.0 / Build 6300. (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19421.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-19421 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-19421 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/cve-2026-19421.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-19421
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-19421"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Zohocorp DDI Central
fixed in 6301
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-19421
Is CVE-2026-19421 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?
An authenticated user can inject input that makes a managed Windows DNS server run arbitrary commands. The commands run with the privileges of the Windows account configured for DDI Central DNS management.Source: manageengine.com
Which versions are affected by CVE-2026-19421?
DDI Central: before 6301.Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists DDI Central 6.3.0 / Build 6300 as affected, in setups where DDI Central manages Windows-backed DNS zones. To check a installation, compare its DDI Central build number with Build 6301, which is the fixed build.Source: manageengine.com
How do I fix CVE-2026-19421?
Upgrade DDI Central to Build 6301, which the advisory names as the fixed version.Source: manageengine.com