CVE-2020-11531 in the critical feed json
The DataEngine Xnode Server application in Zoho ManageEngine DataSecurity Plus prior to 6.0.1 does not validate the database schema name wh…
published 2020-05-08 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-3883
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.7%
- EPSS 13.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
The DataEngine Xnode Server application in Zoho ManageEngine DataSecurity Plus prior to 6.0.1 does not validate the database schema name when handling a DR-SCHEMA-SYNC request. This allows an authenticated attacker to execute code in the context of the product by writing a JSP file to the webroot directory via directory traversal.
Patch / fix
- zohocorp manageengine_adaudit_plus 6.0.1
- zohocorp manageengine_datasecurity_plus 6.0.1
Exploit prediction
13.66% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2020/May/27 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/157604/ManageEngine-DataSecurity-Plus-Path-Traversal-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
seclists.org
/fulldisclosure/2020/May/27
exploit, mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/157604/ManageEngine-DataSecurity-Plus-Path-Traversal-Code-Execution.html
exploit, third-party-advisory, vdb-entry
- pitstop.manageengine.com /portal/community/topic/upgrade-datasecurity-plus-to-the-build-6013-to-fix-security-issues
Sources
- CVE List CVE-2020-11531
- NVD CVE-2020-11531
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.