Skip to main content
CVE-2025-6118VulnerabilityPublished

CVE-2025-6118: Das Parking Management System 停车场管理系统 · SQL Injection

Affects Das Parking Management System 停车场管理系统Source CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Das Parking Management System 停车场管理系统Affected
  • =6.2.0
Fixed in–

AI-suggested

1. Immediate network-level controls: Restrict access to the /vehicle/search API endpoint by implementing IP whitelisting or VPN access to limit exposure to trusted networks only. 2. Web Application Firewall (WAF): Deploy or update WAF rules to detect and block SQL injection patterns targeting the vehicleTypeCode parameter. 3. Input validation and sanitization: If possible, apply strict input validation on vehicleTypeCode to allow only expected values (e.g., predefined codes or numeric ranges) and reject suspicious inputs. 4. Monitoring and logging: Enable detailed logging of API requests and monitor for anomalous query patterns or repeated failed attempts indicative of injection attempts. 5. Vendor engagement: Contact Das for official patches or updates and apply them promptly once available. 6. Segmentation: Isolate the parking management system database from other critical infrastructure to limit lateral movement in case of compromise. 7. Incident response readiness: Prepare to respond to potential data breaches or service disruptions by having backup and recovery plans specific to the parking management system data. 8. Regular security assessments: Conduct penetration testing focused on API endpoints to identify and remediate injection or other vulnerabilities proactively.

Description

A vulnerability was found in Das Parking Management System 停车场管理系统 6.2.0. It has been rated as critical. This issue affects some unknown processing of the file /vehicle/search of the component API. The manipulation of the argument vehicleTypeCode leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…