CVE-2018-8533 json
An information disclosure vulnerability exists in Microsoft SQL Server Management Studio (SSMS) when parsing malicious XML content containi…
published 2018-10-10 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-20157
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 23.4%
- EPSS 23.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
An information disclosure vulnerability exists in Microsoft SQL Server Management Studio (SSMS) when parsing malicious XML content containing a reference to an external entity, aka "SQL Server Management Studio Information Disclosure Vulnerability." This affects SQL Server Management Studio 17.9, SQL Server Management Studio 18.0. This CVE ID is unique from CVE-2018-8527, CVE-2018-8532.
Patch / fix
Timeline
- Published
- First public exploit (EDB-45583)
Exploit prediction
23.37% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-45583 Microsoft SQL Server Management Studio 17.9 - XML External Entity Injection local, 2018-10-11
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Microsoft SQL Server Management Studio 17.9
- Microsoft SQL Server Management Studio 18.0
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8533
patch, vendor-advisory
-
exploit-db.com
/exploits/45583/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1041826
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/105476
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-8533
- NVD CVE-2018-8533
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.