CVE-2024-24110
Description
SQL injection in crmeb_java before v1.3.4 via sortKey parameter in /api/front/spread/people allows arbitrary SQL commands.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
SQL injection in crmeb_java before v1.3.4 via sortKey parameter in /api/front/spread/people allows arbitrary SQL commands.
Vulnerability
SQL injection in crmeb_java <=1.3.4 in /api/front/spread/people endpoint. The sortKey parameter is used in an ORDER BY clause with ${} interpolation without proper sanitization. The vulnerability is exploitable only when the attacker user has at least two promoters in the system [1].
Exploitation
Attacker needs a valid user account with at least two promoters. Send a crafted GET request to /api/front/spread/people with sortKey parameter containing SQL injection payload. Example: sortKey=updatexml(1,concat(0x7e,(select group_concat(table_name) from information_schema.tables where table_schema=database()),0x7e),1) [1].
Impact
Successful exploitation allows the attacker to execute arbitrary SQL commands, potentially leading to data exfiltration, modification, or deletion. The attacker can gain unauthorized access to sensitive database contents [1].
Mitigation
Upgrade to crmeb_java v1.3.4 or later where the issue is fixed. As a workaround, ensure strict input validation on the sortKey parameter [1].
AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- crmeb_java/crmeb_javadescription
- Range: <1.3.4
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.