CVE-2025-9757
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-9757 is a critical SQL injection vulnerability in the Courier Management System version 1.0, specifically in the login function of the /ajax.php file. The vulnerability arises because the 'email' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access, enabling attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 3, 4]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, data leakage, data modification, deletion of data, full system compromise, and potential service disruption. Attackers can remotely exploit this flaw without any authentication, which poses a significant risk to the confidentiality, integrity, and availability of the system and its data. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'email' parameter in the /ajax.php login function for SQL injection. Tools like sqlmap can be used with payloads such as boolean-based blind injection, error-based injection, and time-based blind injection. Example sqlmap usage includes setting a 2-second delay for time-based injections. Specific payloads demonstrated include: - Boolean-based: email=-5982' OR 1461=1461-- nsiq&password=test - Error-based: email=1@1' OR (SELECT 4078 FROM(SELECT COUNT(*),CONCAT(0x7176786b71,(SELECT (ELT(4078=4078,1))),0x7171716a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- FoEr&password=test - Time-based: email=1@1' AND (SELECT 3869 FROM (SELECT(SLEEP(2)))rZpB)-- dIkW&password=test Additionally, Google dorking with queries like inurl:ajax.php can help identify vulnerable targets. [3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. - Enforce strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user privileges by avoiding use of high-privilege accounts (e.g., root or admin) for routine operations. - Conduct regular security audits to detect and address vulnerabilities promptly. - Consider replacing the affected product with an alternative solution if possible. [4, 3]