VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

mantisbt/mantisbt: vulnerability history, versions and safety

mantisbt/mantisbt is a package in the Packagist ecosystem. Vulert records 74 vulnerabilities for it across 78 releases, from Apr 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
74 vulnerabilities recorded C4 H20 M49 L1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
33 in the last 12 months

Most recent disclosure 15 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mantisbt/mantisbt vulnerabilities

Vulert verdict on mantisbt/mantisbt i

Updated on 23 Oct 2026

Careful: 2 of the 74 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 74 vulnerabilities on record across 4 years, 33 in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 74 over 4 years · 33 in the last year i
  • Latest disclosure 15 Jul 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for mantisbt/mantisbt, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.28.3 C3 H3 M3 Yes Details →
2.28.2 C3 H3 M3 Yes Details →
2.28.1 C3 H11 M13 Yes Details →
2.28.0 C4 H12 M13 Yes Details →
2.27.3 C4 H10 M12 Yes Details →
2.27.2 C4 H10 M12 Yes Details →
2.27.1 C4 H11 M15 Yes Details →
2.27.0 C4 H11 M15 Yes Details →
2.26.4 C4 H11 M15 Yes Details →
2.26.3 C4 H11 M16 Yes Details →
2.26.2 C4 H11 M16 Yes Details →
2.26.1 C4 H12 M18 Yes Details →
2.26.0 C4 H13 M17 Yes Details →
2.25.8 C4 H13 M17 Yes Details →
2.25.7 C4 H13 M18 Yes Details →
2.25.6 C4 H13 M18 Yes Details →
2.25.5 C4 H13 M19 Yes Details →
2.25.4 C4 H13 M20 Yes Details →
2.25.3 C4 H13 M20 Yes Details →
2.25.2 C4 H14 M22 No Details →
2.25.1 C4 H14 M23 No Details →
2.25.0 C4 H14 M23 No Details →
2.24.5 C4 H14 M24 No Details →
2.24.4 C4 H15 M24 No Details →
2.24.3 C4 H16 M28 No Details →
2.24.2 C4 H16 M31 No Details →
2.24.1 C4 H16 M32 No Details →
2.24.0 C4 H16 M32 No Details →
2.23.1 C4 H16 M32 No Details →
2.23.0 C4 H16 M32 No Details →
2.22.2 C4 H15 M31 No Details →
2.22.1 C4 H15 M31 No Details →
2.22.0 C4 H15 M31 No Details →
2.21.3 C4 H15 M31 No Details →
2.21.2 C4 H15 M32 No Details →
2.21.1 C4 H15 M33 No Details →
2.21.0 C4 H15 M33 No Details →
2.20.1 C4 H15 M33 No Details →
2.20.0 C4 H15 M33 No Details →
2.19.1 C4 H15 M33 No Details →
2.19.0 C4 H15 M33 No Details →
2.18.1 C4 H15 M33 No Details →
2.18.0 C4 H15 M33 No Details →
2.17.2 C4 H15 M33 No Details →
2.17.1 C4 H15 M35 No Details →
2.17.0 C4 H15 M36 No Details →
2.16.1 C4 H15 M36 No Details →
2.16.0 C4 H15 M36 No Details →
2.15.1 C4 H15 M36 No Details →
2.15.0 C4 H15 M38 No Details →
2.14.0 C4 H15 M38 No Details →
2.13.2 C4 H15 M38 No Details →
2.13.1 C4 H15 M38 No Details →
2.13.0 C4 H15 M38 No Details →
2.12.2 C4 H15 M38 No Details →
2.12.1 C4 H15 M38 No Details →
2.12.0 C4 H15 M38 No Details →
2.11.1 C4 H15 M38 No Details →
2.11.0 C4 H15 M38 No Details →
2.10.1 C4 H14 M38 No Details →
2.10.0 C4 H14 M38 No Details →
2.9.1 C4 H14 M38 No Details →
2.9.0 C4 H14 M38 No Details →
2.8.1 C4 H14 M38 No Details →
2.8.0 C4 H14 M38 No Details →
2.7.1 C4 H14 M37 No Details →
2.7.0 C4 H14 M37 No Details →
2.6.0 C4 H14 M37 No Details →
2.5.2 C4 H14 M37 No Details →
2.5.1 C4 H14 M38 No Details →
2.5.0 C4 H14 M38 No Details →
2.4.2 C4 H14 M38 No Details →
2.4.1 C4 H14 M38 No Details →
2.4.0 C4 H14 M38 No Details →
2.3.3 C4 H14 M38 No Details →
2.3.2 C4 H14 M38 No Details →
2.3.1 C4 H14 M39 No Details →
2.3.0 C4 H14 M39 No Details →

Newest 78 of 78 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 34
  • 2023 2
  • 2024 5
  • 2025 4
  • 2026 29

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 33 of the 74 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mantisbt/mantisbt

The 5 most severe of 74 vulnerabilities recorded for this package

Search all 74 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-30849: MantisBT Authentication Bypass Vulnerability via SOAP API on MySQL 9.3 critical 2.28.1 23 Mar 2026
CVE-2026-47156: MantisBT Critical SOAP API Authentication Bypass and Privilege Escalation 9.3 critical 2.28.4 15 Jul 2026
CVE-2026-52881: MantisBT Reflected XSS Vulnerability in admin/install.php 9.2 critical 2.28.4 15 Jul 2026
CVE-2026-52847: MantisBT Reflected XSS Vulnerability in admin/install.php 9.2 critical 2.28.4 15 Jul 2026
CVE-2017-7615: MantisBT Arbitrary Password Reset Vulnerability 8.8 high 1.3.10 13 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mantisbt/mantisbt

Is mantisbt/mantisbt safe to use?

Vulert records 74 vulnerabilities for mantisbt/mantisbt in Packagist: 4 critical, 20 high, 49 medium and 1 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does mantisbt/mantisbt have?

74 vulnerabilities are recorded for mantisbt/mantisbt in the Packagist ecosystem: 4 critical, 20 high, 49 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mantisbt/mantisbt vulnerabilities disclosed?

33 vulnerabilities were recorded for mantisbt/mantisbt in the last 12 months, and the oldest entry in this database dates to 14 Apr 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mantisbt/mantisbt are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mantisbt/mantisbt for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mantisbt/mantisbt version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.