SDL Web 8.5.0 Content Manager xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in SDL Web 8.5.0. This vulnerability affects unknown code of the component Content Manager. Executing a manipulation can lead to xml external entity reference. This vulnerability is handled as CVE-2018-19371. The attack can be executed remotely. Additionally, an exploit exists.
Details
A vulnerability was found in SDL Web 8.5.0. It has been declared as critical. This vulnerability affects an unknown functionality of the component Content Manager. The manipulation with an unknown input leads to a xml external entity reference vulnerability. The CWE definition for the vulnerability is CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
The SaveUserSettings service in Content Manager in SDL Web 8.5.0 has an XXE Vulnerability that allows reading sensitive files from the system.
The bug was discovered 12/18/2018. The weakness was released 01/02/2019 as EDB-ID 46000 as not defined exploit (Exploit-DB). The advisory is available at exploit-db.com. This vulnerability was named CVE-2018-19371 since 11/20/2018. The exploitation appears to be easy. The attack can be initiated remotely. The successful exploitation needs a single authentication. Technical details are unknown but a public exploit is available.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (46000). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Xml external entity referenceCWE: CWE-611 / CWE-610
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
11/20/2018 🔍12/18/2018 🔍
01/02/2019 🔍
01/02/2019 🔍
01/02/2019 🔍
01/02/2019 🔍
01/03/2019 🔍
11/26/2025 🔍
Sources
Advisory: EDB-ID 46000Status: Not defined
CVE: CVE-2018-19371 (🔍)
GCVE (CVE): GCVE-0-2018-19371
GCVE (VulDB): GCVE-100-128626
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/03/2019 12:42Updated: 11/26/2025 19:20
Changes: 01/03/2019 12:42 (58), 04/25/2020 18:05 (6), 11/26/2025 19:20 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.