The vulnerability exists due to insecure concatenation of configuration data directly into raw SQL strings. Specifically, the history_order configuration value is parsed in core/history_api.php and injected directly into an ORDER BY clause. Because the application applies zero sanitization, string parameterization, or whitelist validation against this configuration value before running the query, an administrator can store a malicious SQL payload that persistently executes when users view bug history.
Published: 2026-07-23
Base Score: 7.5
Vector: CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P
Severity: High
Base Score: 9.8
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Severity: Critical
Base Score: 8.5
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
Severity: High