CVE-2025-8254
BaseFortify
Publication date: 2025-07-28
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-8254 is a critical SQL injection vulnerability in Campcodes Courier Management System version 1.0, specifically in the /view_parcel.php file. The vulnerability occurs because the application directly uses the user-supplied 'ID' parameter in SQL queries without any validation or sanitization. This allows attackers to inject malicious SQL code remotely, enabling them to perform blind SQL injection attacks to access, manipulate, or disrupt the database and system. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized access to the database, leakage of sensitive information, data manipulation, full system control by attackers, and potential disruption of services. Attackers can remotely execute arbitrary SQL commands without authentication, which compromises the confidentiality, integrity, and availability of the system. [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 /view_parcel.php endpoint for SQL injection. Tools like sqlmap can be used to automate detection. Example commands include using sqlmap with the URL containing the vulnerable parameter, e.g., sqlmap -u "http://target/view_parcel.php?id=1" --batch. Manual testing can include injecting payloads such as 'id=2 AND 3381=3381' (boolean-based blind), 'id=2 OR (SELECT 6509 FROM(SELECT COUNT(*),CONCAT(...))a)' (error-based), 'id=2 AND (SELECT 8090 FROM (SELECT(SLEEP(5)))oNAk)' (time-based blind), or 'id=-6068 UNION ALL SELECT NULL,...,CONCAT(...),NULL-- -' (UNION query) to observe the application's response for signs of SQL injection. [3, 2, 1]
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 routine database operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. Additionally, consider replacing the affected software with an alternative product as no fixed version is currently available. [3, 2]