CVE-2025-5778
BaseFortify
Publication date: 2025-06-06
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 |
|---|---|---|
| 1000projects | abc_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-5778 is a critical SQL injection vulnerability in version 1.0 of the ABC Courier Management System, specifically in the /admin or /adminSQL component. The vulnerability occurs because the 'username' parameter is improperly handled and directly used in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data modification or deletion, full system control, and service disruption. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely exploit the system without any authentication. They can gain unauthorized access to the database, leak sensitive data, modify or delete data, take full control of the system, and disrupt services. This poses a serious threat to system security and business continuity. [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 testing the '/admin' endpoint of the ABC Courier Management System version 1.0 for SQL injection on the 'username' parameter. One can use tools like sqlmap to automate detection. Example command using sqlmap: sqlmap -u http://<target-ip>/admin --data="username=1" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads such as: 1) Boolean-based blind SQL injection payload: username=1' OR NOT 2574=2574 # 2) Error-based SQL injection payload: username=1' OR (SELECT 6673 FROM(SELECT COUNT(*),CONCAT(0x71787a6271,(SELECT (ELT(6673=6673,1))),0x7170627871,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- 3) Time-based blind SQL injection payload: username=1' AND (SELECT 9953 FROM (SELECT(SLEEP(5)))nYzL)-- These payloads can be sent via POST requests to the /admin endpoint to check for SQL injection vulnerability. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. 2) Enforce strict input validation and filtering on the 'username' parameter to ensure inputs conform to expected formats. 3) Minimize database user privileges by avoiding use of high-privilege accounts (e.g., root or admin) for routine database operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, consider replacing or updating the affected component or product to a version without this vulnerability. [1, 2, 3]