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.

365,542

Total vulnerabilities in the database

Vulnerabilities for products matching "coldfusion"

Found 3 matching products. Filters apply to all results.

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

adobe / coldfusion

5300 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2018-15960	Medium	September 25, 2018 9/25/18	== 2018 == 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update14 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5 == 2016-update6
CVE-2018-15961	Critical	September 25, 2018 9/25/18	== 2018 == 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update14 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5 == 2016-update6
CVE-2018-15962	Medium	September 25, 2018 9/25/18	== 2018 == 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update14 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5 == 2016-update6
CVE-2018-15963	Medium	September 25, 2018 9/25/18	== 2018 == 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update14 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5 == 2016-update6
CVE-2018-15964	High	September 25, 2018 9/25/18	== 2018 == 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update14 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5 == 2016-update6
CVE-2018-4938	High	May 19, 2018 5/19/18	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5
CVE-2018-4939	Critical	May 19, 2018 5/19/18	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5
CVE-2018-4940	Medium	May 19, 2018 5/19/18	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5
CVE-2018-4941	Medium	May 19, 2018 5/19/18	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5
CVE-2018-4942	High	May 19, 2018 5/19/18	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update13 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4 == 2016-update5
CVE-2017-11283	Critical	December 1, 2017 12/1/17	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4
CVE-2017-11284	Critical	December 1, 2017 12/1/17	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4
CVE-2017-11285	Medium	December 1, 2017 12/1/17	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4
CVE-2017-11286	High	December 1, 2017 12/1/17	== 2016 == 11.0 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update12 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3 == 2016-update4
CVE-2017-3008	Medium	April 27, 2017 4/27/17	== 2016 == 11.0 == 10.0 == 10.0-update1 == 10.0-update10 == 10.0-update11 == 10.0-update12 == 10.0-update13 == 10.0-update14 == 10.0-update15 == 10.0-update16 == 10.0-update17 == 10.0-update18 == 10.0-update19 == 10.0-update2 == 10.0-update20 == 10.0-update21 == 10.0-update22 == 10.0-update3 == 10.0-update4 == 10.0-update5 == 10.0-update6 == 10.0-update7 == 10.0-update8 == 10.0-update9 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3
CVE-2017-3066	Critical	April 27, 2017 4/27/17	== 2016 == 11.0 == 10.0 == 10.0-update1 == 10.0-update10 == 10.0-update11 == 10.0-update12 == 10.0-update13 == 10.0-update14 == 10.0-update15 == 10.0-update16 == 10.0-update17 == 10.0-update18 == 10.0-update19 == 10.0-update2 == 10.0-update20 == 10.0-update21 == 10.0-update22 == 10.0-update3 == 10.0-update4 == 10.0-update5 == 10.0-update6 == 10.0-update7 == 10.0-update8 == 10.0-update9 == 11.0-update1 == 11.0-update10 == 11.0-update11 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 11.0-update9 == 2016-update1 == 2016-update2 == 2016-update3
CVE-2016-4264	Medium	September 1, 2016 9/1/16	<= 10.0 <= 11.0
CVE-2016-4159	Medium	June 16, 2016 6/16/16	== 2016 == 11.0 == 10.0 == 10.0-update1 == 10.0-update10 == 10.0-update11 == 10.0-update12 == 10.0-update13 == 10.0-update14 == 10.0-update15 == 10.0-update16 == 10.0-update17 == 10.0-update18 == 10.0-update19 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update5 == 10.0-update6 == 10.0-update7 == 10.0-update8 == 10.0-update9 == 11.0-update1 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7 == 11.0-update8 == 2016-update1
CVE-2016-1115	Medium	May 11, 2016 5/11/16	== 2016 == 11.0 == 10.0 == 10.0-update1 == 10.0-update10 == 10.0-update11 == 10.0-update12 == 10.0-update13 == 10.0-update14 == 10.0-update15 == 10.0-update16 == 10.0-update17 == 10.0-update18 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update5 == 10.0-update6 == 10.0-update7 == 10.0-update8 == 10.0-update9 == 11.0-update1 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7
CVE-2016-1114	Critical	May 11, 2016 5/11/16	== 2016 == 11.0 == 10.0 == 10.0-update1 == 10.0-update10 == 10.0-update11 == 10.0-update12 == 10.0-update13 == 10.0-update14 == 10.0-update15 == 10.0-update16 == 10.0-update17 == 10.0-update18 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update5 == 10.0-update6 == 10.0-update7 == 10.0-update8 == 10.0-update9 == 11.0-update1 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7
CVE-2016-1113	Medium	May 11, 2016 5/11/16	== 2016 == 11.0 == 10.0 == 10.0-update1 == 10.0-update10 == 10.0-update11 == 10.0-update12 == 10.0-update13 == 10.0-update14 == 10.0-update15 == 10.0-update16 == 10.0-update17 == 10.0-update18 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update5 == 10.0-update6 == 10.0-update7 == 10.0-update8 == 10.0-update9 == 11.0-update1 == 11.0-update2 == 11.0-update3 == 11.0-update4 == 11.0-update5 == 11.0-update6 == 11.0-update7
CVE-2015-8053	Low	November 18, 2015 11/18/15	<= 10.0 <= 11.0
CVE-2015-8052	Low	November 18, 2015 11/18/15	<= 10.0 <= 11.0
CVE-2015-5255	Low	November 18, 2015 11/18/15	<= 10.0 <= 11.0
CVE-2015-0345	Low	April 15, 2015 4/15/15	<= 10.0 <= 11.0
CVE-2014-9166	Medium	December 10, 2014 12/10/14	== 11.0 == 10.0 == 10.0-update1 == 10.0-update10 == 10.0-update11 == 10.0-update12 == 10.0-update13 == 10.0-update14 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update5 == 10.0-update6 == 10.0-update7 == 10.0-update8 == 10.0-update9 == 11.0-update1 == 11.0-update2
CVE-2014-0570	Medium	October 15, 2014 10/15/14	== 9.0.1-update_9 == 9.0.2-update_6 == 11.0 == 9.0.2 == 9.0 == 9.0-update_12 == 10.0 == 9.0.1-update_11 == 9.0.2-update_4 == 9.0.1 == 9.0-update_10 == 10.0-update1 == 10.0-update11 == 10.0-update12 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update8
CVE-2014-0571	Low	October 15, 2014 10/15/14	== 9.0.1-update_9 == 9.0.2-update_6 == 11.0 == 9.0.2 == 9.0 == 9.0-update_12 == 10.0 == 9.0.1-update_11 == 9.0.2-update_4 == 9.0.1 == 9.0-update_10 == 10.0-update1 == 10.0-update11 == 10.0-update12 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update8
CVE-2014-0572	Low	October 15, 2014 10/15/14	== 9.0.1-update_9 == 9.0.2-update_6 == 11.0 == 9.0.2 == 9.0 == 9.0-update_12 == 10.0 == 9.0.1-update_11 == 9.0.2-update_4 == 9.0.1 == 9.0-update_10 == 10.0-update1 == 10.0-update11 == 10.0-update12 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update8
CVE-2014-5315	Low	September 26, 2014 9/26/14	== 8.0 <= 8.0.1
CVE-2013-5326	Low	November 13, 2013 11/13/13	== 9.0.2 == 9.0 == 9.0.1 == 10.0 == 10.0-update1 <= 10.0 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update8
CVE-2013-5328	High	November 13, 2013 11/13/13	== 10.0 == 10.0-update1 <= 10.0 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update8
CVE-2010-5290	High	September 20, 2013 9/20/13	== 9.0 <= 9.0.2 == 9.0.1
CVE-2013-3349	Medium	July 10, 2013 7/10/13	== 9.0.2 == 9.0 == 9.0.1
CVE-2013-3350	High	July 10, 2013 7/10/13	== 10.0 == 10.0-update1 == 10.0-update2 == 10.0-update3 == 10.0-update4 == 10.0-update8
CVE-2013-1389	High	May 16, 2013 5/16/13	== 9.0.1-update_9 == 9.0.2 == 9.0 == 10.0 == 9.0.2-update_4 == 9.0.1 == 9.0-update_10 == 10.0-update1 == 10.0-update3 == 10.0-update4
CVE-2013-3336	Medium	May 9, 2013 5/9/13	== 9.0.2 == 9.0 == 10.0 == 9.0.1
CVE-2013-1387	High	April 10, 2013 4/10/13	== 9.0.2 == 9.0 == 10.0 == 9.0.1 == 10.0-update1 == 10.0-update3 == 10.0-update4
CVE-2013-1388	High	April 10, 2013 4/10/13	== 9.0.2 == 9.0 == 10.0 == 9.0.1 == 10.0-update1 == 10.0-update3 == 10.0-update4
CVE-2013-0632	Critical	January 17, 2013 1/17/13	== 9.0.2 == 9.0 == 10.0 == 9.0.1
CVE-2013-0629	High	January 9, 2013 1/9/13	== 9.0.2 == 9.0 == 10.0 == 9.0.1
CVE-2013-0631	High	January 9, 2013 1/9/13	== 9.0.2 == 9.0 == 9.0.1
CVE-2013-0625	Critical	January 9, 2013 1/9/13	== 9.0.2 == 9.0 == 9.0.1
CVE-2012-5675	Low	December 12, 2012 12/12/12	== 9.0.2 == 9.0 == 10.0 == 9.0.1
CVE-2012-5674	High	November 20, 2012 11/20/12	== 10.0 == 10.0-update1 == 10.0-update3 == 10.0-update4
CVE-2012-2048	Medium	September 12, 2012 9/12/12	== 9.0.2 == 8.0 <= 10.0 == 9.0 == 8.0.1 == 9.0.1
CVE-2012-2041	Low	June 13, 2012 6/13/12	== 8.0 == 9.0 == 8.0.1
CVE-2012-0770	Medium	March 13, 2012 3/13/12	== 8.0 == 9.0 == 8.0.1 == 9.0.1
CVE-2011-4368	Low	December 14, 2011 12/14/11	== 8.0 == 9.0 == 8.0.1 == 9.0.1
CVE-2011-2463	Low	December 14, 2011 12/14/11	== 8.0 == 9.0 == 8.0.1 == 9.0.1

Showing vulnerabilities for 3 products matching "coldfusion". Each product has independent pagination.

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.