Oracle Retail Customer Management and Segmentation Foundation Segment xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as very critical has been found in Oracle Retail Customer Management and Segmentation Foundation 16.0/17.0/18.0/19.0. The affected element is an unknown function of the component Segment. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2020-10683. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Oracle Retail Customer Management and Segmentation Foundation 16.0/17.0/18.0/19.0. It has been classified as very critical. This affects some unknown processing of the component Segment. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 01/20/2021 as Oracle Critical Patch Update Advisory - January 2021. The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2020-10683. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/22/2026).
We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 294867 (Oracle Siebel Server <= 25.11 (January 2026 CPU)), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (294867). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 294867
Nessus Name: Oracle Siebel Server <= 25.11 (January 2026 CPU)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
03/20/2020 🔍01/20/2021 🔍
01/20/2021 🔍
01/20/2021 🔍
01/22/2026 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - January 2021
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-10683 (🔍)
GCVE (CVE): GCVE-0-2020-10683
GCVE (VulDB): GCVE-100-168405
Entry
Created: 01/20/2021 19:47Updated: 01/22/2026 12:10
Changes: 01/20/2021 19:47 (38), 02/17/2021 18:03 (6), 02/17/2021 18:06 (18), 01/22/2026 12:10 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.