Description

A flaw has been found in code-projects Task Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/AdminLogin.php. Executing a manipulation of the argument email/password can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-08-09T08:16:47.710Z",
  "pubdate": "2026-08-09T08:16:47.710Z",
  "executiveSummary": "A SQL injection vulnerability has been identified in the code-projects Task Management System 1.0, specifically within the administrative authentication interface. The flaw resides in the handling of input parameters within the /admin/AdminLogin.php file, allowing unauthenticated remote attackers to manipulate the email and password fields. Successful exploitation of this vulnerability enables adversaries to bypass authentication mechanisms, execute arbitrary database queries, and potentially gain full administrative control over the underlying database management system. Given that an exploit has been publicly published, the risk of active exploitation by malicious actors is elevated, threatening the confidentiality, integrity, and availability of the affected system.",
  "technicalDetails": "The vulnerability is classified as a SQL injection (SQLi) flaw stemming from improper input validation and insecure database query construction within the /admin/AdminLogin.php file of the code-projects Task Management System 1.0. The root cause lies in the direct concatenation or lack of parameterization of user-supplied input—specifically the email and password parameters—into dynamic SQL statements executed against the backend database.\nExploitation of this vulnerability is performed remotely over the network without requiring prior authentication or privileged access. An attacker interacts with the administrative login form at /admin/AdminLogin.php and supplies specially crafted SQL payloads within the email and/or password input fields. Because the application fails to properly sanitize or parameterize these inputs, the injected SQL syntax is interpreted directly by the database engine as executable commands rather than literal string data.\nThe attack flow proceeds as follows: First, the remote adversary intercepts or directly accesses the /admin/AdminLogin.php endpoint. Second, the attacker injects malicious SQL syntax (such as tautologies like 'OR '1'='1) into the authentication parameters. Third, the vulnerable script processes the request and executes the malformed SQL query. Fourth, the database evaluates the injected logic, resulting in authentication bypass, unauthorized administrative session creation, or the extraction of sensitive database contents. Post-exploitation impact includes complete compromise of the administrative interface, unauthorized data access, and potential escalation of privileges depending on database user permissions."
}