GHSA-mw6p-33vw-46cc: MantisBT: SQL Injection via history_order Configuration Value
MantisBT versions 2.28.3 and earlier contain a SQL injection vulnerability in core/history_api.php. The vulnerability arises because the history_order configuration value is used directly in a SQL ORDER BY clause without sanitization or validation. An administrator can set this value via the web UI or REST API, enabling injection that triggers when any user views a bug with history entries. This can lead to sensitive data exposure and, with certain MySQL privileges, remote code execution.
AI Analysis
Technical Summary
MantisBT before version 2.28.4 is vulnerable to SQL injection due to the unsanitized use of the history_order configuration value in an ORDER BY clause within core/history_api.php. An administrator can inject malicious SQL via the web UI or REST API configuration endpoints. The injected SQL executes when any authenticated user views a bug's history, potentially exposing sensitive database contents including user credentials, API tokens, and private issues. If the MySQL user has FILE privileges, the attacker can write a PHP webshell to the web root, achieving remote code execution. A patch fixing this issue was committed in version 2.28.4.
Potential Impact
Exploitation allows extraction of sensitive data from the bugtracker database such as user credentials, API tokens, and private issue data. Additionally, if the MySQL FILE privilege is granted, full remote code execution is possible by writing a PHP webshell to the server. The injection requires an administrator to plant the payload once, after which any authenticated user viewing a bug with history triggers the malicious SQL execution.
Mitigation Recommendations
A patch fixing this vulnerability is available in MantisBT version 2.28.4. Users should upgrade to version 2.28.4 or later to remediate this issue. No alternative workarounds or temporary mitigations are specified in the advisory. Administrators should avoid setting the history_order configuration value to untrusted input until patched.
GHSA-mw6p-33vw-46cc: MantisBT: SQL Injection via history_order Configuration Value
Description
MantisBT versions 2.28.3 and earlier contain a SQL injection vulnerability in core/history_api.php. The vulnerability arises because the history_order configuration value is used directly in a SQL ORDER BY clause without sanitization or validation. An administrator can set this value via the web UI or REST API, enabling injection that triggers when any user views a bug with history entries. This can lead to sensitive data exposure and, with certain MySQL privileges, remote code execution.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
MantisBT before version 2.28.4 is vulnerable to SQL injection due to the unsanitized use of the history_order configuration value in an ORDER BY clause within core/history_api.php. An administrator can inject malicious SQL via the web UI or REST API configuration endpoints. The injected SQL executes when any authenticated user views a bug's history, potentially exposing sensitive database contents including user credentials, API tokens, and private issues. If the MySQL user has FILE privileges, the attacker can write a PHP webshell to the web root, achieving remote code execution. A patch fixing this issue was committed in version 2.28.4.
Potential Impact
Exploitation allows extraction of sensitive data from the bugtracker database such as user credentials, API tokens, and private issue data. Additionally, if the MySQL FILE privilege is granted, full remote code execution is possible by writing a PHP webshell to the server. The injection requires an administrator to plant the payload once, after which any authenticated user viewing a bug with history triggers the malicious SQL execution.
Mitigation Recommendations
A patch fixing this vulnerability is available in MantisBT version 2.28.4. Users should upgrade to version 2.28.4 or later to remediate this issue. No alternative workarounds or temporary mitigations are specified in the advisory. Administrators should avoid setting the history_order configuration value to untrusted input until patched.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mw6p-33vw-46cc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-47142"]
- Ecosystems
- ["Packagist"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a58b51668715ace43db3b24
Added to database: 07/16/2026, 10:40:22 UTC
Last enriched: 07/16/2026, 14:28:34 UTC
Last updated: 07/17/2026, 01:54:24 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.