mantisbt/mantisbt
Affected
- introduced
0, fixed2.28.4(ecosystem)
Fixed versions
2.28.4
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-47142
MantisBT: SQL Injection via history_order Configuration Value
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
Patches
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Resources
Credits
McCaulay Hudson (@McCaulay) of watchTowr
High Basis: The source's own band: HIGH
0, fixed 2.28.4 (ecosystem)2.28.4
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0