Vulnerability Database

326,895

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

Composer icon

mantisbt / mantisbt

119 vulnerabilities found
Title Severity Exploit Date Affected Version
Low November 4, 2025 11/4/25
< 2.27.2
Medium November 4, 2025 11/4/25
< 2.27.2
Critical November 4, 2025 11/4/25
< 2.27.2
Medium November 4, 2025 11/4/25
< 2.27.2
Medium September 30, 2024 9/30/24
< 2.26.4
Medium May 14, 2024 5/14/24
< 2.26.2
Medium May 14, 2024 5/14/24
< 2.26.2
High May 14, 2024 5/14/24
< 2.26.2
High February 20, 2024 2/20/24
< 2.26.1
Low October 16, 2023 10/16/23
< 2.25.8
Low February 23, 2023 2/23/23
< 2.25.6
Medium June 24, 2022 6/24/22
< 2.25.5
Medium May 4, 2022 5/4/22
< 2.25.2
High April 14, 2022 4/14/22
< 2.25.3
Medium April 13, 2022 4/13/22
< 2.25.3
Medium June 17, 2021 6/17/21
< 2.25.2
High March 7, 2021 3/7/21
< 2.24.5
Medium February 22, 2021 2/22/21
<= 2.24.3
Low January 29, 2021 1/29/21
< 2.24.4
Medium January 29, 2021 1/29/21
< 2.24.4
Low January 29, 2021 1/29/21
< 2.24.4
Medium December 30, 2020 12/30/20
== 2.24.3
High December 30, 2020 12/30/20
< 2.24.4
Low September 30, 2020 9/30/20
< 2.24.3
Low September 30, 2020 9/30/20
< 2.24.3
Low September 30, 2020 9/30/20
< 2.24.3
Medium August 12, 2020 8/12/20
< 2.24.2
Medium March 19, 2020 3/19/20
< 2.21.3
Medium November 9, 2019 11/9/19
>= 1.2.0 < 1.2.2
Low November 7, 2019 11/7/19
< 1.2.13
Low October 31, 2019 10/31/19
>= 1.2.12 < 1.2.15
Medium October 31, 2019 10/31/19
== 1.2.14
Medium October 31, 2019 10/31/19
== 1.2.13
Medium October 31, 2019 10/31/19
== 1.2.0-rc1
== 1.2.0-rc2
>= 1.2.1 <= 1.2.14
== 1.2.0
High October 9, 2019 10/9/19
>= 2.0.0 < 2.22.1
>= 1.0.0 < 1.3.20
Medium August 21, 2019 8/21/19
>= 2.13.0 <= 2.21.1
Low June 20, 2019 6/20/19
>= 2.1.0 <= 2.17.0
Low June 6, 2019 6/6/19
== 2.0.0
<= 1.3.14
Low October 30, 2018 10/30/18
>= 2.1.0 <= 2.17.1
Low October 30, 2018 10/30/18
>= 2.1.0 <= 2.17.1
Low August 3, 2018 8/3/18
>= 2.1.0 <= 2.15.0
Low August 3, 2018 8/3/18
>= 2.0.0 <= 2.15.0
Medium February 2, 2018 2/2/18
<= 2.10.0
Low January 30, 2018 1/30/18
== 2.10.0
Medium September 12, 2017 9/12/17
<= 1.2.18
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
Low August 9, 2017 8/9/17
== 1.3.0-beta1
<= 1.2.18
Low August 5, 2017 8/5/17
== 2.5.2
Medium August 1, 2017 8/1/17
>= 1.3.0 < 1.3.12
>= 2.0.0 < 2.5.2
Low August 1, 2017 8/1/17
== 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

Frequently Asked Questions

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.