Quick answers
- Is CVE-2026-47142 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47142 being exploited in the wild.
- How severe is CVE-2026-47142?
- High severity, with a CVSS score of 4, published 15 July 2026.
- Which products and versions are affected?
- MantisBT <= 2.28.3; mantisbt/mantisbt (Packagist) <= 2.28.3, ECOSYSTEM:introduced=0,fixed=2.28.4.
- Is there a fix for CVE-2026-47142?
- 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-47142 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-47142?
- 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
A SQL injection vulnerability exists in MantisBT versions 2.28.3 and earlier within 'core/history_api.php'. The 'history_order' configuration value is concatenated directly into a SQL 'ORDER BY' clause without sanitization or whitelist validation. An attacker with administrative privileges can set this value via the web UI or REST API. The payload is executed whenever any authenticated user views a bug with history entries. This can lead to the extraction of sensitive data (credentials, API tokens) or Remote Code Execution (RCE) if the database user has the 'FILE' privilege, enabling the creation of a web shell.
Affected products
- MantisBT MantisBT <= 2.28.3
Identifiers
- CVE-2026-47142
- GHSA-mw6p-33vw-46cc
Timeline
- 2026-07-15: disclosed
- 2026-07-15: advisory
- 2026-07-15: patched: Fixed in version 2.28.4