Quick answers
- Is CVE-2026-49273 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49273 being exploited in the wild.
- How severe is CVE-2026-49273?
- High severity, with a CVSS score of 4, published 15 July 2026.
- Which products and versions are affected?
- MantisBT >= 1.3.0, <= 2.28.3; mantisbt/mantisbt (Packagist) >= 1.3.0, <= 2.28.3, ECOSYSTEM:introduced=1.3.0,fixed=2.28.4.
- Is there a fix for CVE-2026-49273?
- 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-49273 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-49273?
- 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
MantisBT 2.28.3 and earlier is vulnerable to remote code execution via eval() injection in adm_config_set.php. When a non-string configuration value is set, it is processed by ConfigParser and Tokenizer, which executes eval() on the input. Although a 'return;' statement is prepended to prevent execution, PHP's compile-time hoisting allows an attacker to define a class or function within the eval'd string. This defined class can hijack a class intended to be loaded later by the PHP autoloader. Exploitation requires administrative privileges and allows execution of arbitrary code as the web server user. The issue is patched in version 2.28.4.
Affected products
- MantisBT MantisBT >= 1.3.0, <= 2.28.3
Identifiers
- CVE-2026-49273
- GHSA-v84x-qvhg-f36r
Timeline
- 2026-07-15: disclosed
- 2026-07-15: advisory
- 2026-07-15: patched