CVE-2025-9759
BaseFortify
Publication date: 2025-09-01
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| campcodes | courier_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9759 is a critical SQL injection vulnerability in the Campcodes/SourceCodester Courier Management System version 1.0. It affects the signup function in the /ajax.php file, where user inputs such as 'lastname', 'firstname', and 'email' are not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database by accessing, modifying, or deleting data without authorization. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, data leakage, modification or deletion of sensitive information, and potentially full system compromise or service disruption. Because the attack can be performed remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the affected system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for SQL injection attempts targeting the '/ajax.php' file, specifically the 'lastname' parameter in the signup function. You can monitor web server logs for suspicious requests containing SQL injection payloads in the 'lastname', 'email', or 'firstname' parameters. Additionally, using Google dorking with queries like 'inurl:ajax.php' can help identify vulnerable instances exposed on the internet. For active testing, tools like sqlmap can be used to test the '/ajax.php' endpoint for SQL injection by sending crafted requests targeting the 'lastname' parameter. Example command: sqlmap -u "http://target.com/ajax.php" --data="lastname=TEST" -p lastname --batch [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements to handle user inputs securely, ensuring that inputs such as 'lastname', 'firstname', and 'email' are strictly validated and sanitized to conform to expected formats. Minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations. Conduct regular security audits to detect and address vulnerabilities promptly. Since no official patch or fix is available, consider replacing the affected product with a secure alternative if possible. [2, 3]