Quick answers
- Is CVE-2026-40607 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40607 being exploited in the wild.
- How severe is CVE-2026-40607?
- High severity, with a CVSS score of 4, published 11 May 2026.
- Which products and versions are affected?
- MantisBT >= 2.1.0, <= 2.28.1; mantisbt/mantisbt (Packagist) >= 2.1.0, <= 2.28.1, ECOSYSTEM:introduced=2.1.0,fixed=2.28.2.
- Is there a fix for CVE-2026-40607?
- 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-40607 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-40607?
- 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 stored cross-site scripting (XSS) vulnerability exists in MantisBT due to incorrect escaping of a saved filter's owner name. The vulnerability is triggered when the configuration option '$g_show_user_realname' is set to ON, allowing an attacker to inject arbitrary HTML/JavaScript via the owner column. While the attack vector is network-based, exploitation typically requires 'Manager' access level or higher to save filters publicly. Successful exploitation allows for arbitrary code execution in the context of a victim's browser session. A patch has been released in version 2.28.2, and workarounds include disabling the real name display or restricting filter creation permissions.
Affected products
- MantisBT MantisBT >= 2.1.0, <= 2.28.1
Identifiers
- CVE-2026-40607
- GHSA-f633-865q-2mhh
Timeline
- 2026-05-11: disclosed
- 2026-05-11: advisory