CVE-2026-47142

highcovered by 1 sourcefirst seen 2026-07-15

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 - https://github.com/mantisbt/mantisbt/commit/6ad20bea2e01f33c6e4170775ae4d9dbe2c75325 Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Resources - https://mantisbt.org/bugs/view.php?id=37123 Credits McCaulay Hudson (@McCaulay) of watchTowr

⚡ Watch CVE-2026-47142

Get an email if CVE-2026-47142 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Advisory coverage (1)

highGHSA-mw6p-33vw-46cc: MantisBT: SQL Injection via history_order Configuration Valueghsa · 2026-07-15

External references

NVD record for CVE-2026-47142

CVE.org record

Embed the live status

— this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2026-47142 status](https://www.csirts.com/badge/CVE-2026-47142)](https://www.csirts.com/cve/CVE-2026-47142)