SQL injection vulnerability in the CIGESv2 system

The SQL injection vulnerability resides within the /ajaxConfigTotem.php file of CIGESv2, specifically within the 'id' parameter. Successful exploitation allows an attacker to craft malicious SQL queries that bypass security measures and directly access the underlying database. This could lead to the complete exfiltration of all data stored within the database, including user credentials, configuration information, and potentially other sensitive business data. The impact is severe, as a successful attack could compromise the confidentiality and integrity of the entire system. There is no immediate precedent for similar exploitation patterns in publicly disclosed incidents, but the potential for widespread data compromise is significant.

Organizations utilizing CIGESv2, particularly those with publicly accessible instances or those lacking robust input validation practices, are at significant risk. Shared hosting environments where multiple users share the same CIGESv2 instance are especially vulnerable, as a compromise of one user's account could potentially lead to the compromise of the entire system.

• linux / server: Monitor database logs for unusual SQL queries targeting /ajaxConfigTotem.php. Use journalctl -f to observe real-time log activity.

journalctl -f | grep "/ajaxConfigTotem.php" | grep -i "select"

• generic web: Use curl to test the /ajaxConfigTotem.php endpoint with various payloads. Examine the response for signs of SQL injection (e.g., database errors, unexpected data).

curl 'http://your-cigesv2-server/ajaxConfigTotem.php?id=1' 2>&1 | grep -i "error"

• database (mysql): If you have access to the MySQL database, run queries to check for unauthorized data access or modification.

SELECT * FROM users WHERE username LIKE '%attacker%';

1. 2024-03-22Disclosure

   disclosure

2. 2024-03-22Patch

   patch

1. Réservé2024-03-20
2. Publiée2024-03-22
3. Modifiée2024-08-13
4. EPSS mis à jour2026-04-02

The primary mitigation for CVE-2024-2722 is to immediately upgrade CIGESv2 to version 2.0.1 or later. If an immediate upgrade is not feasible due to compatibility issues or system downtime constraints, consider implementing temporary workarounds. While not a complete solution, input validation and sanitization on the 'id' parameter within /ajaxConfigTotem.php can help reduce the attack surface. Web application firewalls (WAFs) configured to detect and block SQL injection attempts targeting this specific endpoint can also provide an additional layer of protection. Monitor database logs for suspicious SQL queries that might indicate an ongoing attack. After upgrade, confirm by attempting a query through /ajaxConfigTotem.php and verifying that it does not result in a database error or data leakage.