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.

354,808

Total vulnerabilities in the database

Vulnerabilities for products matching "mantisbt"

Found 1 matching product.

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

mantisbt / mantisbt

1636 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2017-6973	Medium	May 17, 2022 5/17/22	== 2.1.0 == 2.0.0-rc1 == 2.1.2 == 1.3.4 == 2.1.3 == 1.3.0-rc2 == 2.0.0-beta3 == 2.1.1 == 2.2.1 == 1.3.7 == 1.3.3 == 2.0.1 == 1.3.8 == 2.0.0-beta2 == 1.3.9 == 1.3.2 == 1.3.5 == 2.0.0-beta1 == 2.0.0 == 1.3.6 == 2.0.0-rc2 == 1.3.1 == 2.2.0 < 1.3.8 >= 2.0.0 < 2.1.2 >= 2.2.0 < 2.2.2
CVE-2017-7241	Medium	May 17, 2022 5/17/22	== 2.3.0 == 2.1.0 == 2.0.0-rc1 == 2.1.2 == 1.3.4 == 2.1.3 == 1.3.0-rc2 == 2.0.0-beta3 == 1.3.0-beta1 == 1.3.0-beta3 == 1.2.18 == 2.1.1 == 2.2.2 == 2.2.1 == 1.3.0-rc1 == 1.3.7 == 1.2.19 == 1.3.3 == 2.0.1 == 1.3.8 == 2.0.0-beta2 == 1.3.9 == 1.2.16 == 1.3.2 == 1.3.5 == 2.0.0-beta1 == 2.2.3 == 1.2.17 == 2.0.0 == 1.3.6 == 1.2.20 == 2.0.0-rc2 == 1.3.1 == 2.2.0 == 1.3.0-beta2 < 1.3.9 >= 2.0.0 < 2.1.3 >= 2.2.0 < 2.2.3
CVE-2017-7309	Medium	May 17, 2022 5/17/22	== 2.1.0 == 2.0.0-rc1 == 2.1.2 == 1.3.4 == 2.1.3 == 1.3.0-rc2 == 2.0.0-beta3 == 2.1.1 == 2.2.2 == 2.2.1 == 1.3.7 == 1.3.3 == 2.0.1 == 1.3.8 == 2.0.0-beta2 == 1.3.9 == 1.3.2 == 1.3.5 == 2.0.0-beta1 == 2.0.0 == 1.3.6 == 2.0.0-rc2 == 1.3.1 == 2.2.0 < 1.3.9 >= 2.1.0 < 2.1.3 >= 2.2.0 < 2.2.3
CVE-2017-12062	Medium	May 17, 2022 5/17/22	== 2.3.0 == 2.1.0 == 2.1.2 == 2.4.1 == 2.1.3 == 2.5.0 == 2.4.2 == 2.1.1 == 2.2.2 == 2.2.1 == 2.5.1 == 2.4.0 == 2.3.2 == 2.2.4 == 2.3.3 == 2.2.3 == 2.3.1 == 2.2.0 >= 2.0.0 < 2.5.2
CVE-2018-14504	Medium	May 14, 2022 5/14/22	>= 2.0.0 <= 2.15.0 >= 2.0.0 < 2.15.1
CVE-2018-13055	Medium	May 14, 2022 5/14/22	>= 2.1.0 <= 2.15.0 >= 2.1.0 < 2.15.1
CVE-2010-2574	Low	May 14, 2022 5/14/22	== 1.2.2
CVE-2018-17782	Medium	May 14, 2022 5/14/22	>= 2.1.0 <= 2.17.1 >= 2.1.0 < 2.17.2
CVE-2018-17783	Medium	May 14, 2022 5/14/22	>= 2.1.0 <= 2.17.1 >= 2.1.0 < 2.17.2
CVE-2017-7615	High	May 13, 2022 5/13/22	<= 2.3.0 >= 1.3.0-rc.2 < 1.3.10 >= 2.0.0 < 2.2.4 >= 2.3.0 < 2.3.1
CVE-2017-12061	Medium	May 13, 2022 5/13/22	>= 1.3.0 < 1.3.12 >= 2.0.0 < 2.5.2
CVE-2022-28508	Medium	May 5, 2022 5/5/22	< 2.25.2 <= 2.25.2
CVE-2009-20001	High	April 21, 2022 4/21/22	< 2.24.5
CVE-2021-43257	High	April 15, 2022 4/15/22	< 2.25.3
CVE-2022-26144	Medium	April 14, 2022 4/14/22	< 2.25.3
CVE-2009-2802	Medium	November 9, 2019 11/9/19	>= 1.2.0 < 1.2.2
CVE-2013-1811	Low	November 7, 2019 11/7/19	< 1.2.13
CVE-2013-1930	Low	October 31, 2019 10/31/19	>= 1.2.12 < 1.2.15
CVE-2013-1931	Medium	October 31, 2019 10/31/19	== 1.2.14
CVE-2013-1932	Medium	October 31, 2019 10/31/19	== 1.2.13
CVE-2013-1934	Medium	October 31, 2019 10/31/19	== 1.2.0-rc1 == 1.2.0-rc2 >= 1.2.1 <= 1.2.14 == 1.2.0
CVE-2018-9839	Low	June 6, 2019 6/6/19	== 2.0.0 <= 1.3.14
CVE-2018-6526	Medium	February 2, 2018 2/2/18	<= 2.10.0
CVE-2018-6382	Low	January 30, 2018 1/30/18	== 2.10.0
CVE-2014-9624	Medium	September 12, 2017 9/12/17	<= 1.2.18
CVE-2015-2046	Low	August 28, 2017 8/28/17	== 1.2.13 == 1.2.15 == 1.2.18 == 1.2.19 == 1.2.16 == 1.2.17 == 1.2.14
CVE-2014-9701	Low	August 9, 2017 8/9/17	== 1.3.0-beta1 <= 1.2.18
CVE-2017-12419	Low	August 5, 2017 8/5/17	== 2.5.2
CVE-2015-5059	Low	August 1, 2017 8/1/17	<= 1.2.19
CVE-2017-7222	Low	March 22, 2017 3/22/17	<= 2.1.0
CVE-2017-6799	Low	March 10, 2017 3/10/17	<= 2.2.0
CVE-2017-6797	Low	March 10, 2017 3/10/17	< 1.3.7 >= 2.0.0 < 2.2.1
CVE-2016-5364	Low	February 17, 2017 2/17/17	<= 1.2.19
CVE-2016-6837	Low	January 10, 2017 1/10/17	== 1.3.0-beta1 <= 1.2.18 == 2.0.0-beta1
CVE-2014-9759	Medium	April 11, 2016 4/11/16	== 1.3.0-rc1
CVE-2014-8987	Low	August 24, 2015 8/24/15	== 1.2.13 == 1.2.15 == 1.2.16 == 1.2.17 == 1.2.14
CVE-2015-1042	Medium	February 10, 2015 2/10/15	== 1.2.13 == 1.2.15 == 1.2.2 == 1.2.0-rc1 == 1.2.12 == 1.2.18 == 1.2.5 == 1.2.10 == 1.2.9 == 1.2.8 == 1.2.16 == 1.2.11 == 1.2.3 == 1.2.6 == 1.2.1 == 1.2.7 == 1.2.17 == 1.2.4 == 1.2.0-rc2 == 1.2.14 == 1.2.0-alpha3
CVE-2014-9573	Medium	January 26, 2015 1/26/15	== 1.3.0-beta1 <= 1.2.18
CVE-2014-9572	High	January 26, 2015 1/26/15	== 1.3.0-beta1 <= 1.2.18
CVE-2014-9571	Low	January 26, 2015 1/26/15	== 1.3.0-beta1 <= 1.2.18
CVE-2014-9272	Low	January 9, 2015 1/9/15	== 1.2.13 == 1.1.0-rc3 == 1.2.15 == 1.2.2 == 1.2.0-rc1 == 1.2.12 == 1.2.5 == 1.2.10 == 1.2.9 == 1.1.0-rc2 == 1.1.6 == 1.2.0 == 1.1.9 == 1.1.4 == 1.2.8 == 1.1.0-a4 == 1.2.16 == 1.1.0-rc1 == 1.1.0-a2 == 1.2.11 == 1.1.5 == 1.1.0-a3 == 1.2.3 == 1.1.2 == 1.1.0-a1 == 1.2.6 == 1.2.1 == 1.1.7 == 1.1.3 == 1.1.8 == 1.2.7 == 1.2.17 == 1.2.4 == 1.2.0-rc2 == 1.2.14 == 1.1.1 == 1.2.0-alpha1 == 1.2.0-alpha2 == 1.2.0-alpha3
CVE-2014-9271	Medium	January 9, 2015 1/9/15	== 1.2.13 == 1.1.0-rc3 == 1.2.15 == 1.2.2 == 1.2.0-rc1 == 1.2.12 == 1.2.5 == 1.2.10 == 1.2.9 == 1.1.0-rc2 == 1.1.6 == 1.2.0 == 1.1.9 == 1.1.4 == 1.2.8 == 1.1.0-a4 == 1.2.16 == 1.1.0-rc1 == 1.1.0-a2 == 1.2.11 == 1.1.5 == 1.1.0-a3 == 1.2.3 == 1.1.2 == 1.1.0-a1 == 1.2.6 == 1.2.1 == 1.1.7 == 1.1.3 == 1.1.8 == 1.2.7 == 1.2.17 == 1.2.4 == 1.2.0-rc2 == 1.2.14 == 1.1.1 == 1.2.0-alpha1 == 1.2.0-alpha2 == 1.2.0-alpha3
CVE-2014-9269	Low	January 9, 2015 1/9/15	== 1.2.13 == 1.1.0-rc3 == 1.2.0a1 == 1.2.15 == 1.2.0a2 == 1.2.2 == 1.2.0-rc1 == 1.2.12 == 1.2.5 == 1.2.10 == 1.2.9 == 1.1.0-rc2 == 1.1.6 == 1.2.0 == 1.1.9 == 1.1.4 == 1.2.8 == 1.1.0-a4 == 1.2.16 == 1.1.0-rc1 == 1.1.0-a2 == 1.2.11 == 1.1.5 == 1.1.0-a3 == 1.2.3 == 1.1.2 == 1.1.0-a1 == 1.2.6 == 1.2.1 == 1.1.7 == 1.1.3 == 1.1.8 == 1.2.7 == 1.2.17 == 1.2.4 == 1.2.0-rc2 == 1.2.14 == 1.1.1 == 1.2.0-alpha1 == 1.2.0-alpha2 == 1.2.0-alpha3
CVE-2014-9506	Low	January 4, 2015 1/4/15	<= 1.2.17
CVE-2014-9388	Medium	December 17, 2014 12/17/14	<= 1.2.17
CVE-2014-8553	Medium	December 17, 2014 12/17/14	<= 1.2.17
CVE-2014-6316	Medium	December 12, 2014 12/12/14	<= 1.2.17
CVE-2014-9281	Low	December 9, 2014 12/9/14	<= 1.2.17
CVE-2014-9280	High	December 8, 2014 12/8/14	<= 1.2.17
CVE-2014-9279	Medium	December 8, 2014 12/8/14	== 1.0.0-rc1 == 1.2.13 == 1.0.0-rc3 == 1.0.0-a3 == 1.1.0-rc3 == 1.2.15 == 1.0.2 == 1.2.0-rc1 == 1.2.12 == 1.2.10 == 1.0.9 == 1.1.0-rc2 == 1.1.6 == 1.2.0 == 1.1.9 == 1.1.4 == 1.0.3 == 1.1.0 == 1.0.0-rc2 == 1.1.0-a4 == 1.2.16 == 1.1.0-rc1 == 1.1.0-a2 == 1.2.11 == 1.1.5 == 1.0.7 == 1.1.0-a3 == 1.1.2 == 1.0.1 == 1.1.0-a1 == 1.0.0-rc5 == 1.2.1 == 1.0.4 == 1.1.7 == 1.1.3 == 1.0.5 == 1.1.8 == 1.2.17 == 1.0.0-rc4 == 1.2.0-rc2 == 1.0.6 == 1.0.8 == 1.2.14 == 1.1.1 == 1.2.0-alpha1 == 1.2.0-alpha2 == 1.2.0-alpha3

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.