CVE-2025-6118
BaseFortify
Publication date: 2025-06-16
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 |
|---|---|---|
| das | parking_management_system | 6.2.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-6118 is a critical SQL injection vulnerability in Das Parking Management System version 6.2.0. It affects the API endpoint /vehicle/search, where the vehicleTypeCode parameter is improperly handled. This allows an attacker to inject malicious SQL commands remotely without authentication, potentially accessing or manipulating sensitive data in the system. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing unauthorized attackers to access, modify, or delete sensitive data within the Das Parking Management System. It compromises the confidentiality, integrity, and availability of the system, potentially leading to data breaches, service disruption, and unauthorized data manipulation. [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 API endpoint `/vehicle/search` for SQL injection via the `vehicleTypeCode` parameter. You can use tools like curl or sqlmap to send crafted requests to this endpoint and observe if SQL injection is possible. For example, using curl: `curl -G 'http://<target>/vehicle/search' --data-urlencode 'vehicleTypeCode=1'` and then try injecting SQL payloads such as `' OR '1'='1` to see if the response indicates SQL injection. Alternatively, sqlmap can be used to automate detection: `sqlmap -u 'http://<target>/vehicle/search?vehicleTypeCode=1' --batch`. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability. It is suggested to consider replacing the affected product. As immediate steps, restrict access to the vulnerable API endpoint if possible, monitor for suspicious activity, and apply any available updates or patches from the vendor once released. [2]