ManageEngine DataSecurity Plus versions before 6310 are vulnerable to an agent authentication…
CVE-2026-18911 is a high-severity improper input validation vulnerability in ManageEngine DataSecurity Plus from Zoho, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 6310 as the first without the flaw, so updating ManageEngine DataSecurity Plus to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.86% chance of exploitation within 30 days, higher than 80% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update ManageEngine DataSecurity Plus to 6310 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Zoho | ManageEngine DataSecurity Plus | before 6310 | 6310 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N. Scored by CNA.
Official description
ManageEngine DataSecurity Plus versions before 6310 are vulnerable to an agent authentication bypass, allowing unenrolled agents to send requests without proper authentication.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
References
Other references
Other vulnerabilities in ManageEngine DataSecurity Plus
- 8.4 High severity
- 8.1 High severity
Recent Improper Input Validation vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 9.4 Critical severity
- 8.7 High severity
Spotted an error? Tell us.