High

MantisBT: SQL Injection via history_order Configuration Value

  • Disclosed: 15.07.2026
  • Updated: 11.10.2026 10:22

MantisBT 2.28.3 and earlier versions contains a SQL injection vulnerability in core/history_api.php. The history_order configuration value is concatenated directly into a SQL ORDER BY clause without any sanitisation, parameterization, or validation against a whitelist.

An administrator can set this configuration value via the web UI (adm_config_set.php) or the REST API (PATCH /api/rest/config). The injected SQL then executes whenever any user views a bug with history entries.

Impact

  • Sensitive data extraction from the entire bugtracker database including user credentials (cookie_string, password hashes), API tokens, and private issue data
  • With MySQL FILE privilege: full RCE via INTO OUTFILE writing a PHP webshell to the web root
  • The admin plants the payload once; any authenticated user viewing a bug with history triggers the injection

Patches

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Resources

Credits

McCaulay Hudson (@McCaulay) of watchTowr

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package mantisbt/mantisbt < 2.28.4 2.28.4

References

CVSS score -
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-89
Platform
Composer
Package
mantisbt/mantisbt
Disclosed
15.07.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-mw6p-33vw-46cc - CC BY 4.0

Vulnerability history: mantisbt/mantisbt

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (74) in the archive
Total entries
74
First → latest
04.2022 07.2026
Without a fix
2
Exploited in attacks
0

Severity breakdown

  • Critical 4
  • High 20
  • Medium 49
  • Low 1

Disclosures per year

  1. 2022: 34
  2. 2023: 2
  3. 2024: 5
  4. 2025: 4
  5. 2026: 29
Severity:
  1. High CVE-2026-62944 < 2.28.4 2.28.4
  2. Critical CVE-2026-52847 < 2.28.4 2.28.4
  3. MantisBT: SQL Injection via history_order Configuration Value this entry
    High CVE-2026-47142 < 2.28.4 2.28.4
  4. High CVE-2026-44657 < 2.28.2 2.28.2
  5. High CVE-2026-44655 >= 1.3.0, < 2.28.2 2.28.2
  6. High CVE-2026-42071 >= 2.23.0, < 2.28.2 2.28.2
  7. High CVE-2026-40607 >= 2.1.0, < 2.28.2 2.28.2
  8. High · 6.1 CVE-2026-33548 >= 2.28.0, < 2.28.2 2.28.2
  9. High CVE-2026-33517 >= 2.28.0, < 2.28.1 2.28.1
  10. High · 8.3 CVE-2024-23830 < 2.26.1 2.26.1
Show more (4) Showing 20 of 24

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.