CodeAstro Leave Management System SQL Injection Vulnerability

A SQL injection vulnerability, identified as CVE-2026-8132, has been discovered in CodeAstro Leave Management System version 1.0. The vulnerability resides in the /login.php file and is triggered by manipulating the txt_username argument. Successful exploitation allows for remote attackers to inject arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. Publicly available exploit code increases the likelihood of active exploitation. This vulnerability poses a significant threat to organizations using the affected software.

Attack Chain

1. Attacker identifies a CodeAstro Leave Management System 1.0 instance.
2. The attacker crafts a malicious HTTP POST request targeting /login.php.
3. The txt_username parameter in the POST request is injected with a SQL payload (e.g., admin'--).
4. The application fails to properly sanitize the input, passing the malicious SQL code to the database.
5. The database executes the injected SQL command.
6. If successful, the attacker bypasses authentication and gains unauthorized access.
7. The attacker can then access sensitive information, modify existing records, or potentially execute arbitrary code on the database server.

Impact

Successful exploitation of this SQL injection vulnerability (CVE-2026-8132) can lead to unauthorized access to sensitive employee data, including personal information, leave records, and potentially payroll information. An attacker could also modify or delete data, disrupt operations, or gain complete control over the database server. Given the ease of exploitation and the availability of public exploits, organizations using CodeAstro Leave Management System 1.0 are at high risk.

Recommendation

• Apply the vendor-supplied patch or upgrade to a secure version of CodeAstro Leave Management System to remediate CVE-2026-8132.
• Deploy the Sigma rule Detect CodeAstro Leave Management System SQL Injection Attempt to identify potential exploitation attempts targeting the /login.php endpoint.
• Implement input validation and sanitization measures to prevent SQL injection attacks, focusing on the txt_username parameter in /login.php.
• Monitor web server logs for suspicious POST requests to /login.php containing SQL injection payloads, as described in the attack chain.