CVE-2019-10273 json
Information leakage vulnerability in the /mc login page in ManageEngine ServiceDesk Plus 9.3 software allows authenticated users to enumera…
published 7y ago modified 4mo ago also EUVD-2019-2276
- cvss
- 4.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.6%
- EPSS 7.6% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Information leakage vulnerability in the /mc login page in ManageEngine ServiceDesk Plus 9.3 software allows authenticated users to enumerate active users. Due to a flaw within the way the authentication is handled, an attacker is able to login and verify any active account.
Is CVE-2019-10273 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-46674)
Exploit prediction
7.64% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46674 ManageEngine ServiceDesk Plus 9.3 - User Enumeration webapps, 2019-04-08
- 0x445.github.io https://0x445.github.io/CVE-2019-10273/ referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/152439/ManageEngine-ServiceDesk-Plus-9.3-User-Enumeration.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
exploit-db.com
/exploits/46674/
exploit, third-party-advisory, vdb-entry
-
0x445.github.io
/CVE-2019-10273/
exploit, third-party-advisory
-
packetstormsecurity.com
/files/152439/ManageEngine-ServiceDesk-Plus-9.3-User-Enumeration.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2019-10273
- NVD CVE-2019-10273
Fencer Intel 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.