Description

A vulnerability was identified in code-projects Task Management System 1.0. This affects the function Operation::select_with_multiple_condition of the file /index.php of the component Login Form. Such manipulation of the argument email leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-08-18T13:17:43.097Z",
  "pubdate": "2026-08-18T13:17:43.097Z",
  "executiveSummary": "A vulnerability has been identified in code-projects Task Management System 1.0, specifically within the Login Form component. The weakness stems from improper handling of user-supplied input, resulting in a SQL Injection vulnerability.\nThe flaw exists in the function Operation::select_with_multiple_condition located in the file /index.php. An unauthenticated remote attacker can exploit this security deficiency by manipulating the vulnerable email parameter during the authentication or login process.\nSuccessful exploitation of this SQL injection vulnerability allows an adversary to interfere with the underlying database queries executed by the application. This manipulation can lead to unauthorized access to sensitive information, bypass of authentication mechanisms, and potential compromise of the underlying database management system.\nThe risk implications are critical as the exploit is publicly available, lowering the barrier to entry for potential threat actors. Remote exploitation requires network connectivity to the target web application without requiring prior authentication or specific user privileges, exposing vulnerable deployments to immediate compromise.",
  "technicalDetails": "The vulnerability resides in the code-projects Task Management System 1.0 application, specifically inside the Operation::select_with_multiple_condition function called during the processing of requests to /index.php.\nThe root cause of the vulnerability is the lack of proper input sanitization, type enforcement, and parameterized queries or prepared statements when handling the email argument supplied via the Login Form component.\nAttackers can leverage this flaw by injecting malicious SQL payload syntax into the email parameter fields exposed by the web interface. Because the input is directly concatenated or unsafely interpolated into the database query string within Operation::select_with_multiple_condition, the database interpreter parses the injected control characters and SQL commands as part of the intended query logic.\nThe attack flow proceeds as follows: First, the remote adversary interacts with the Login Form component exposed over the network via HTTP/HTTPS protocols. Second, the attacker crafts a malicious input string containing SQL commands designed to alter the logic of the authentication query, appending it to the vulnerable email parameter. Third, the HTTP request is submitted to /index.php. Fourth, the application passes the tainted email argument directly into the vulnerable database interaction function without adequate validation. Finally, the database executes the modified query, returning unauthorized result sets or confirming authentication bypass based on the injected payload behavior.\nNetwork exposure is fully remote, as the Login Form component is accessible over standard web ports. No prior authentication or elevated privileges are required to initiate the attack vector.\nPost-exploitation impact includes unauthorized data exfiltration, modification or deletion of database records, potential administrative privilege escalation, and complete compromise of the underlying database instance depending on database user permissions."
}