How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "retail_xstore_point_of_service"

Found 1 matching product.

You can search for specific versions with /product/retail_xstore_point_of_service/1.2.3

oracle / retail_xstore_point_of_service

523 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2018-15756	High	October 18, 2018 10/18/18	== 7.1
CVE-2018-3126	Medium	October 17, 2018 10/17/18	== 15.0.2 == 16.0.4 == 17.0.2
CVE-2018-11797	Medium	October 5, 2018 10/5/18	== 17.0
CVE-2018-11763	Low	September 25, 2018 9/25/18	== 7.1 == 7.0
CVE-2018-8032	Medium	August 2, 2018 8/2/18	== 7.1
CVE-2018-1000613	Critical	July 9, 2018 7/9/18	== 7.1 == 7.0
CVE-2018-12536	Medium	June 27, 2018 6/27/18	== 15.0 == 16.0.0 == 7.1 == 17.0
CVE-2017-7658	Critical	June 26, 2018 6/26/18	== 15.0 == 7.1 == 16.0 == 17.0
CVE-2017-7657	Critical	June 26, 2018 6/26/18	== 15.0 == 7.1 == 16.0 == 17.0
CVE-2018-11039	Medium	June 25, 2018 6/25/18	== 7.1
CVE-2018-11040	High	June 25, 2018 6/25/18	== 7.1
CVE-2018-1000180	Medium	June 5, 2018 6/5/18	== 7.1 == 7.0
CVE-2018-1258	High	May 11, 2018 5/11/18	== 17.0
CVE-2018-10237	Medium	April 26, 2018 4/26/18	== 15.0 == 7.1 == 16.0 == 17.0
CVE-2018-2840	Medium	April 19, 2018 4/19/18	== 7.1.6 == 7.0.6 == 6.5.11 == 15.0.1 == 16.0.2
CVE-2018-1270	Critical	April 6, 2018 4/6/18	== 7.1
CVE-2018-1271	Medium	April 6, 2018 4/6/18	== 7.1
CVE-2018-1199	Medium	March 16, 2018 3/16/18	== 7.1
CVE-2017-15707	Medium	December 1, 2017 12/1/17	== 7.1.6 == 7.0.6 == 6.5.11 == 15.0.1 == 16.0.2
CVE-2017-10427	Medium	October 19, 2017 10/19/17	== 7.1.6 == 7.0.6 == 6.5.11 == 6.0.11 == 15.0.1
CVE-2017-12617	High	October 4, 2017 10/4/17	== 7.1.6 == 7.0.6 == 6.0.11 == 15.0.1
CVE-2017-10214	Medium	August 8, 2017 8/8/17	== 15.0 == 16.0.0 == 7.1.3 == 7.0.3 == 7.0.4 == 7.1 == 7.1.6 == 7.0.2 == 7.1.5 == 7.1.1 == 7.0.6 == 7.0.5 == 6.5.11 == 7.0 == 6.0.10 == 7.1.4 == 6.5.4 == 6.0.11 == 15.0.1 == 6.5.10 == 7.1.2 == 7.0.1
CVE-2017-10183	Medium	August 8, 2017 8/8/17	== 15.0 == 16.0.0 == 7.1.3 == 7.0.3 == 7.0.4 == 7.1 == 7.1.6 == 7.0.2 == 7.1.5 == 7.1.1 == 7.0.6 == 7.0.5 == 6.5.11 == 7.0 == 6.0.10 == 7.1.4 == 6.5.4 == 6.0.11 == 15.0.1 == 6.5.10 == 7.1.2 == 7.0.1
CVE-2017-9735	High	June 16, 2017 6/16/17	== 15.0 == 7.1 == 16.0 == 17.0
CVE-2016-3429	Medium	April 21, 2016 4/21/16	== 7.1 == 5.0 == 6.5 == 5.5 == 6.0 == 7.0

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.