Is CVE-2026-49280 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49280 being exploited in the wild.

How severe is CVE-2026-49280?

Medium severity, with a CVSS score of 4, published 15 July 2026.

Which products and versions are affected?

MantisBT >= 2.8.0, = 2.8.0, <= 2.28.3, ECOSYSTEM:introduced=2.8.0,fixed=2.28.4.

Is there a fix for CVE-2026-49280?

Yes. mantisbt/mantisbt (Packagist): upgrade to 2.28.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-49280 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-49280?

Check whether you run MantisBT or mantisbt/mantisbt (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49280: MantisBT unauthorized issue status change in REST and SOAP API

Q: Is there a fix for CVE-2026-49280?

Yes. mantisbt/mantisbt (Packagist): upgrade to 2.28.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-49280 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-49280?

Check whether you run MantisBT or mantisbt/mantisbt (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49280 · Severity: medium · CVSS 4 · Published 2026-07-15

MantisBT is a popular open-source bug tracking system. A vulnerability in its API allows users with low-level 'Updater' permissions to change the status of issues even when the system is configured to require higher 'Developer' permissions for such actions. This could allow unauthorized users to disrupt project workflows or prematurely close bug reports.

Technologies: MantisBT, mantisbt/mantisbt (Packagist). Vendors: MantisBT, Packagist.

Quick answers

Is CVE-2026-49280 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49280 being exploited in the wild.
How severe is CVE-2026-49280?: Medium severity, with a CVSS score of 4, published 15 July 2026.
Which products and versions are affected?: MantisBT >= 2.8.0, <= 2.28.3; mantisbt/mantisbt (Packagist) >= 2.8.0, <= 2.28.3, ECOSYSTEM:introduced=2.8.0,fixed=2.28.4.
Is there a fix for CVE-2026-49280?: Yes. mantisbt/mantisbt (Packagist): upgrade to 2.28.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49280 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49280?: Check whether you run MantisBT or mantisbt/mantisbt (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

mantisbt/mantisbt (Packagist): upgrade to 2.28.4 or later
```
composer require mantisbt/mantisbt:^2.28.4
```

Technical details

A missing authorization check (CWE-862) in the MantisBT REST and SOAP APIs allows users with the $g_update_bug_threshold (typically 'Updater') to modify an issue's status. This occurs even if the $g_set_status_threshold configuration is set to a more restrictive level, such as 'Developer'. An authenticated attacker with network access to the API can exploit this to bypass intended workflow restrictions and modify issue metadata. The issue is resolved in version 2.28.4.

Affected products

MantisBT MantisBT >= 2.8.0, <= 2.28.3

Identifiers

CVE-2026-49280
GHSA-m7ph-9558-mrx3

Timeline

2026-07-15: disclosed
2026-07-15: advisory
2026-07-15: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.