CVE-2025-8186
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 critical SQL injection flaw in the Campcodes Courier Management System version 1.0, specifically in the /edit_branch.php file. It occurs because the application directly uses the user-supplied 'id' parameter in SQL queries without any validation or filtering. This allows attackers to inject arbitrary SQL code remotely, using techniques such as Boolean-based blind injection, error-based injection, time-based blind injection, and UNION query injection. Exploiting this vulnerability can let attackers extract or manipulate database information and execute unauthorized SQL commands. [1, 2, 3]
How can this vulnerability impact me? :
The vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, modification or tampering of data, full system control by attackers, and potential disruption of services. This poses significant risks 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_branch.php file for SQL injection using tools like sqlmap. Commands such as `sqlmap -u "http://target/edit_branch.php?id=1" --batch --dbs` can be used to check for SQL injection vulnerabilities by attempting Boolean-based, error-based, time-based, and UNION query injections. Additionally, vulnerable targets can be identified using Google dorking with the query `inurl:edit_branch.php` to find exposed instances. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats; 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations; 4) Conducting regular security audits to identify and fix vulnerabilities promptly. If possible, consider replacing the affected component with an alternative product. [1, 2, 3]