Analyst readout for executives and security teams
Plain-English summary
This flaw affects Das Parking Management System 6.2.0. A remote attacker may abuse an API export function to inject SQL through the Value argument, potentially exposing or changing parking records and disrupting the system. Public exploit material is referenced, but the bundle does not show confirmed active exploitation.
Executive priority
Treat this as high priority if the product is deployed or externally reachable. Public exploit availability raises urgency, but absence from KEV and incomplete vendor guidance mean response should focus on exposure reduction, monitoring, and vendor confirmation.
Technical view
CVE-2026-9551 is reported as SQL injection in ParkingRecord/ExportParkingRecords, involving xp_cmdshell handling and the Value argument. The CVSS v2 vector indicates network access, low complexity, no authentication, and partial confidentiality, integrity, and availability impact. CWE mappings include CWE-74 and CWE-89.
Likely exposure
Exposure is likely limited to organizations running Das Parking Management System 6.2.0, especially where the affected API endpoint is reachable from untrusted networks. The provided CPE uses a wildcard version range, but the stated affected version is 6.2.0.
Exploitation context
The source bundle says exploit material is publicly available and may be used. KEV is false, and no cited source in the bundle confirms active exploitation in the wild. Vendor response and official remediation information are not present.
Researcher notes
Evidence is primarily from VulDB/CVE data. The report identifies remote unauthenticated SQL injection through Value in an export endpoint and mentions xp_cmdshell. Do not assume additional affected versions or a vendor patch without new source evidence.
Mitigation direction
- Identify any Das Parking Management System 6.2.0 deployments.
- Check Das or integrator guidance for patches or supported mitigations.
- Restrict external access to ParkingRecord/ExportParkingRecords where possible.
- Limit API access to trusted networks and authenticated users.
- Monitor application, database, and WAF logs for suspicious export activity.
- Escalate to vendor support if no advisory is available.
Validation and detection
- Confirm the installed product and exact version from asset records.
- Map whether the affected API endpoint is internet or partner reachable.
- Review logs for unusual requests to ParkingRecord/ExportParkingRecords.
- Check database logs for unexpected command execution indicators.
- Verify compensating controls are enforced at network and application layers.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9551 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 10 6.4 VulDB CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 3.9 3.4 VulDB CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 3.9 3.4 VulDB 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 — — VulDB Vulnerability scoring details
Base CVSS 4.0 score
6.9 MediumVector: 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
Base CVSS 3.1 score
7.3 HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
7.3 HighVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
7.5 HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- VDB-365610 | Das Parking Management System 停车场管理系统 API Endpoint ExportParkingRecords xp_cmdshell sql injection CVE reference, VulDB · vdb-entry, technical-description
- VDB-365610 | CTI Indicators (IOB, IOC, TTP, IOA) CVE reference, VulDB · signature, permissions-required
- Submit #815456 | Shenzhen DAS INTELLITECH Co., Ltd. Parking Management System 6.2.0 SQL Injection CVE reference, VulDB · third-party-advisory
- https://ucn9h68n9289.feishu.cn/wiki/XW9QwcTjCixlLiklQfBcJCcYn0e?from=from_copylink CVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.