CVE-2018-11586 in the critical feed json
XML external entity (XXE) vulnerability in api/rest/status in SearchBlox 8.6.7 allows remote unauthenticated users to read arbitrary files…
published 2018-06-05 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-3612
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.7%
- EPSS 14.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
XML external entity (XXE) vulnerability in api/rest/status in SearchBlox 8.6.7 allows remote unauthenticated users to read arbitrary files or conduct server-side request forgery (SSRF) attacks via a crafted DTD in an XML request.
Timeline
- First public exploit (EDB-44827)
- Published
Exploit prediction
14.70% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-44827 SearchBlox 8.6.7 - XML External Entity Injection webapps, 2018-06-04
- packetstormsecurity.com http://packetstormsecurity.com/files/148032/SearchBlox-8.6.7-XML-External-Entity-Injection.html referenced PoC, tagged "exploit" by a source, unverified
- gurelahmet.com https://gurelahmet.com/searchblox-8-6-7-out-of-band-xml-external-entity-oob-xxe-cve-2018-11586/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
References
-
exploit-db.com
/exploits/44827/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/148032/SearchBlox-8.6.7-XML-External-Entity-Injection.html
exploit, third-party-advisory, vdb-entry
-
gurelahmet.com
/searchblox-8-6-7-out-of-band-xml-external-entity-oob-xxe-cve-2018-11586/
exploit, third-party-advisory
Sources
- CVE List CVE-2018-11586
- NVD CVE-2018-11586
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.