Quick answers
- Is CVE-2026-42070 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42070 being exploited in the wild.
- How severe is CVE-2026-42070?
- Medium severity, with a CVSS score of 4, published 28 May 2026.
- Which products and versions are affected?
- MantisBT < 2.28.2, <= 2.28.1; mantisbt/mantisbt (Packagist) <= 2.28.1, ECOSYSTEM:introduced=0,fixed=2.28.2.
- Is there a fix for CVE-2026-42070?
- Yes. mantisbt/mantisbt (Packagist): upgrade to 2.28.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42070 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42070?
- 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.2 or later
composer require mantisbt/mantisbt:^2.28.2
Technical details
An incorrect authorization vulnerability (CWE-863) exists in the mc_issue_update() function of MantisBT. While the dedicated mc_issue_note_update() function correctly enforces a 'DEVELOPER' threshold, the general issue update API fails to properly validate permissions for bugnote modifications. This allows an authenticated attacker with 'UPDATER' privileges to edit notes, change time tracking data, and toggle the visibility of private notes belonging to higher-privileged users. The issue is addressed in version 2.28.2.
Affected products
- MantisBT MantisBT <= 2.28.1
Identifiers
- CVE-2026-42070
- GHSA-pq86-j2c2-47f6
Timeline
- 2026-05-09: disclosed
- 2026-05-11: advisory
- 2026-05-28: other: NVD published