CVE-2025-8189
BaseFortify
Publication date: 2025-07-26
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-8189 is a critical SQL injection vulnerability in Campcodes Courier Management System 1.0, specifically in the /edit_user.php file. It occurs because the application improperly handles the 'ID' parameter, allowing attackers to inject malicious SQL code due to lack of input sanitization. This enables attackers to manipulate the SQL queries executed by the system, potentially compromising the database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely exploit the system without authentication to extract sensitive database information, manipulate or delete data, gain unauthorized access, and potentially take full control of the system or cause service disruptions. It affects the confidentiality, integrity, and availability of the system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'id' parameter in the /edit_user.php file for SQL injection flaws. Commands using sqlmap can be employed to detect the vulnerability, for example: sqlmap -u "http://target/edit_user.php?id=3" --batch --dbs. Additionally, manual testing with payloads such as 'id=3 AND 2612=2612' (boolean-based blind), 'id=3 OR (SELECT 7317 FROM(SELECT COUNT(*),CONCAT(...))a)' (error-based), or time-based payloads like 'id=3 AND 5003=(SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.COLUMNS B, INFORMATION_SCHEMA.COLUMNS C WHERE 0 XOR 1)' can be used to confirm the injection point. Attackers also use Google dorking with queries like inurl:edit_user.php to identify vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding high-privilege accounts for the application's database connections. 4) Conducting regular security audits of code and systems to identify and remediate vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [2, 1]