Summary
MantisBT: REST API unauthorized Issue status change
A MantisBT user having $g_update_bug_threshold (UPDATER by default) can change an Issue's Status via REST and SOAP API, even if the $g_set_status_threshold config is set to a higher level (DEVELOPER by default).
Workarounds
None
Resources
Credits
Mamdouh Mahfouz (@mamdouhmahfouz)
Impact
Unauthorized change in Issue workflow.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Frequently Asked Questions
- What is CVE-2026-49280? CVE-2026-49280 is a medium-severity missing authorization vulnerability in mantisbt/mantisbt (composer), affecting versions >= 2.8.0, <= 2.28.3. It is fixed in 2.28.4. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of mantisbt/mantisbt are affected by CVE-2026-49280? mantisbt/mantisbt (composer) versions >= 2.8.0, <= 2.28.3 is affected.
- Is there a fix for CVE-2026-49280? Yes. CVE-2026-49280 is fixed in 2.28.4. Upgrade to this version or later.
- Is CVE-2026-49280 exploitable, and should I be worried? Whether CVE-2026-49280 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-49280 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-49280? Upgrade
mantisbt/mantisbtto 2.28.4 or later.