Is CVE-2026-52882 exploited in the wild?

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

How severe is CVE-2026-52882?

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

Which products and versions are affected?

mantisbt/mantisbt (Packagist) <= 2.28.3, ECOSYSTEM:introduced=0,fixed=2.28.4.

Is there a fix for CVE-2026-52882?

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-52882 attacked?

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

Am I affected by CVE-2026-52882?

Check whether you run 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-52882: MantisBT authorization bypass in REST and SOAP APIs

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

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-52882 attacked?

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

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

Check whether you run 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-52882 · 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 permissions to assign unreleased product versions to issues, bypassing intended administrative restrictions. This could lead to data inconsistency or the unauthorized disclosure of upcoming product version names within the tracking system.

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

Quick answers

Is CVE-2026-52882 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-52882 being exploited in the wild.
How severe is CVE-2026-52882?: Medium severity, with a CVSS score of 4, published 15 July 2026.
Which products and versions are affected?: mantisbt/mantisbt (Packagist) <= 2.28.3, ECOSYSTEM:introduced=0,fixed=2.28.4.
Is there a fix for CVE-2026-52882?: 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-52882 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-52882?: Check whether you run 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

An authorization bypass vulnerability (CWE-639) exists in the REST and SOAP APIs of MantisBT. The issue update logic fails to properly enforce the '_report_issues_for_unreleased_versions_threshold_' configuration when processing requests through these APIs. An authenticated attacker with low privileges can exploit this to assign unreleased product versions to bug reports, a task normally restricted to higher-privileged users. This issue is fixed in version 2.28.4.

Affected products

MantisBT MantisBT <= 2.28.3

Identifiers

CVE-2026-52882
GHSA-3v2j-6fw9-f57c

Timeline

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

References

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