Quick answers
- Is CVE-2026-52847 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52847 being exploited in the wild.
- How severe is CVE-2026-52847?
- Critical severity, with a CVSS score of 4, published 15 July 2026.
- Which products and versions are affected?
- mantisbt/mantisbt (Packagist) <= 2.28.3, ECOSYSTEM:introduced=0,fixed=2.28.4.
- Is there a fix for CVE-2026-52847?
- 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-52847 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-52847?
- Check whether you run 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 contains six reflected XSS injection points in /admin/install.php due to user-supplied parameters being echoed into HTML without escaping via the print_test_result() function. While a Content Security Policy (CSP) is present, it lacks a form-action directive, which allows attackers to bypass script execution restrictions to perform credential phishing via form injection, CSS-based UI manipulation, and <meta> tag open redirects. No authentication is required for exploitation. The vulnerability is addressed in version 2.28.4; a recommended workaround is to remove the /admin directory after installation.
Affected products
- MantisBT MantisBT <= 2.28.3
Identifiers
- CVE-2026-52847
- GHSA-77x8-3v3h-hrhv
Timeline
- 2026-07-15: disclosed
- 2026-07-15: patched: Fixed in version 2.28.4
- 2026-07-15: advisory