Quick answers
- Is CVE-2026-41897 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41897 being exploited in the wild.
- How severe is CVE-2026-41897?
- Medium severity, with a CVSS score of 4, published 28 May 2026.
- Which products and versions are affected?
- MantisBT >= 1.0.0, < 2.28.2; mantisbt/mantisbt (Packagist) >= 1.0.0, < 2.28.2, ECOSYSTEM:introduced=1.0.0,fixed=2.28.2.
- Is there a fix for CVE-2026-41897?
- 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-41897 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-41897?
- 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
A reflected cross-site scripting (XSS) vulnerability exists in MantisBT due to a lack of validation of the 'filter_target' parameter in 'return_dynamic_filters.php'. This component is typically used via AJAX on the 'View Issues' page. If the target is a TEXTAREA custom field, an attacker can inject arbitrary HTML and JavaScript. Exploitation requires network access and low privileges (PR:L), allowing an attacker to execute scripts in the context of a user's session. The issue is fixed in version 2.28.2.
Affected products
- MantisBT MantisBT >= 1.0.0, < 2.28.2
Identifiers
- CVE-2026-41897
- GHSA-j7v9-f46r-2rp4
Timeline
- 2026-05-11: advisory: GitHub Advisory published
- 2026-05-28: disclosed: NVD publication