CVE-2025-8230
BaseFortify
Publication date: 2025-07-27
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 Campcodes Courier Management System version 1.0, specifically in the /manage_user.php file. It occurs because the application directly uses the user-supplied "id" parameter in SQL queries without any validation or sanitization. This allows attackers to inject arbitrary SQL code, enabling them to manipulate the database queries. Various SQL injection techniques such as boolean-based blind, error-based, time-based blind, and UNION query injections can be used to exploit this flaw remotely without authentication. The vulnerability compromises the confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, leakage of sensitive data, data tampering, full system compromise, and disruption of services. Attackers can extract or manipulate data, potentially causing severe damage to system security and business continuity. Since the exploit is publicly available and can be executed remotely without authentication, the risk of exploitation is significant. [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 "id" parameter in the /manage_user.php file for SQL injection flaws. One approach is to use SQL injection testing tools such as sqlmap against the target URL, for example: sqlmap -u "http://target/manage_user.php?id=1" --batch. Additionally, attackers or testers can use Google dorking with queries like "inurl:manage_user.php" to identify potentially vulnerable targets. Manual testing can include injecting payloads such as 'id=1 AND (SELECT SLEEP(5))' to observe time delays indicating time-based blind SQL injection. Example payloads include boolean-based, error-based, time-based, and UNION query injections targeting the "id" parameter. [1, 2, 3]
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 injection. 2) Apply strict input validation and filtering on the "id" parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts such as root or admin for application database connections. 4) Conduct regular security audits to identify and remediate vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative, as no known direct patches are reported. [2, 3, 1]