CVE-2018-16793 in the critical feed json
Rollup 18 for Microsoft Exchange Server 2010 SP3 and previous versions has an SSRF vulnerability via the username parameter in /owa/auth/lo…
published 2018-09-21 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-8593
- cvss
- 8.6
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.3%
- EPSS 11.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
Rollup 18 for Microsoft Exchange Server 2010 SP3 and previous versions has an SSRF vulnerability via the username parameter in /owa/auth/logon.aspx in the OWA (Outlook Web Access) login page.
Exploit prediction
11.33% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/149411/Rollup-18-For-Microsoft-Exchange-Server-2010-SP3-Server-Side-Request-Forgery.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2018/Sep/20 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org https://seclists.org/bugtraq/2018/Sep/38 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.6 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
-
packetstormsecurity.com
/files/149411/Rollup-18-For-Microsoft-Exchange-Server-2010-SP3-Server-Side-Request-Forgery.html
exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2018/Sep/20
mailing-list, exploit, third-party-advisory
-
seclists.org
/bugtraq/2018/Sep/38
mailing-list, exploit, issue-tracking, third-party-advisory
-
securityfocus.com
/bid/105386
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-16793
- NVD CVE-2018-16793
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.