Summary
Workarounds
None.
Credits
Thanks to Vishal Shukla for discovering and responsibly reporting the issue.
Impact
MantisBT allows an authenticated user to upload attachments to private Issues they are not authorized to access.
CVE-2026-34754 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.28.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
- b262b4d2835b81394d75356dead66e52a6275206
Frequently Asked Questions
- What is CVE-2026-34754? CVE-2026-34754 is a medium-severity security vulnerability in mantisbt/mantisbt (composer), affecting versions <= 2.28.1. It is fixed in 2.28.2.
- How severe is CVE-2026-34754? CVE-2026-34754 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of mantisbt/mantisbt are affected by CVE-2026-34754? mantisbt/mantisbt (composer) versions <= 2.28.1 is affected.
- Is there a fix for CVE-2026-34754? Yes. CVE-2026-34754 is fixed in 2.28.2. Upgrade to this version or later.
- Is CVE-2026-34754 exploitable, and should I be worried? Whether CVE-2026-34754 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-34754 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-34754? Upgrade
mantisbt/mantisbtto 2.28.2 or later.