CVE-2025-8187
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?
This vulnerability is a SQL injection flaw in the Campcodes Courier Management System version 1.0, specifically in the /edit_parcel.php file. It occurs because the application uses the user-supplied "id" parameter directly in SQL queries without validation or filtering, allowing attackers to inject arbitrary SQL code. This can be exploited remotely using various SQL injection techniques such as boolean-based blind, error-based, time-based blind, and UNION query injections. Attackers can manipulate the database queries to extract, modify, or delete data, or even take full control of the system. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability allows attackers to gain unauthorized access to the database, leak sensitive information, modify or delete data, take full control of the affected system, and potentially cause service interruptions. This poses a severe threat to system security and business continuity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "id" parameter in the /edit_parcel.php file for SQL injection using various techniques such as boolean-based blind, error-based, time-based blind, and UNION query injections. Example payloads include: - Boolean-based blind: id=(SELECT (CASE WHEN (9680=9680) THEN 1 ELSE (SELECT 6700 UNION SELECT 7621) END)) - Error-based injection: id=1 OR (SELECT 6236 FROM(SELECT COUNT(*),CONCAT(0x716b6a6271,(SELECT (ELT(6236=6236,1))),0x7170787071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) - Time-based blind: id=1 OR SLEEP(5) - UNION query injection with 18 columns: id=-1441 UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x716b6a6271,0x4a4b6342465a45754d5a5877576c4a6c6262444e61476263777a6a50424763514970774c4b4c7556,0x7170787071),NULL,NULL,NULL,NULL-- - These payloads can be tested manually or by using automated tools such as sqlmap to confirm the presence of the vulnerability and extract database information. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Use prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. 2. Implement strict input validation and filtering to ensure that inputs conform to expected formats. 3. Minimize database user permissions by avoiding the use of high-privilege accounts (e.g., root or admin) for routine database operations. 4. Conduct regular security audits to identify and remediate vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative until a patch or fix is available. [1, 2, 3]