CVE-2025-9757

7.3

Campcodes / SourceCodester · Courier Management System

The Courier Management System 1.0 contains an unauthenticated SQL injection vulnerability in the login function of the ajax.php file, allowing for remote exploitation.

Executive summary

A critical SQL injection vulnerability in the Courier Management System allows unauthenticated remote attackers to manipulate database queries via the email parameter.

Vulnerability

This vulnerability is a SQL injection flaw (CWE-89) located in the login function within the ajax.php file. The application fails to properly sanitize the email input, allowing an unauthenticated remote attacker to inject malicious SQL commands.

Business impact

Successful exploitation of this vulnerability could allow an attacker to bypass authentication, access sensitive data stored in the database, or interfere with system operations. Given the CVSS score of 7.3, this represents a high-risk security gap that could lead to unauthorized data disclosure and compromise of the application integrity.

Remediation

Immediate Action: As no official patch is currently available, administrators should restrict access to the login interface and the vulnerable ajax.php endpoint using network-level controls.

Proactive Monitoring: Monitor server access logs for anomalous requests to the ajax.php file, specifically looking for SQL-related characters or patterns in the email parameter.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeting the application login flow.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists as documented in the GitHub issue tracker referenced by the vulnerability record.

Analyst recommendation

Given the availability of a public proof-of-concept and the lack of a vendor-supplied patch, users of the Courier Management System 1.0 are at significant risk. Organizations must prioritize isolating the affected component from the public internet and implementing strict input validation or WAF filtering to prevent unauthorized database access until a secure version is released.

Sources

Originally found and disclosed by M00n_L33 (VulDB User), per the CVE Program record.