Live Active security incident? Get immediate response
CVE Record

CVE-2026-9552: Das Parking Management System 停车场管理系统 Search API Endpoint sql injection

A security flaw has been discovered in Das Parking Management System 停车场管理系统 6.2.0. This vulnerability affects unknown code of the component Search API Endpoint. The manipulation of the argument Value results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

HighCVSS 7.5Not KEV-listed Updated
Glexia's Take high

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-9552 is a SQL injection in Das Parking Management System 6.2.0. A remote attacker may be able to abuse the Search API’s Value parameter to affect data confidentiality, integrity, and availability. The public sources say exploit material exists, but they do not show confirmed active exploitation.

Executive priority

Treat this as a high-priority exposure review for parking-management environments. Public exploit material and unauthenticated network reachability increase urgency, but current sources do not prove active exploitation or provide a vendor patch.

Technical view

The vulnerability affects the Search API Endpoint in Das Parking Management System 停车场管理系统 6.2.0. The reported weakness is SQL injection via the Value argument, mapped to CWE-89 and CWE-74. CVSS v2 is 7.5 with network access, low complexity, and no authentication required.

Likely exposure

Exposure is most likely for organizations running Das Parking Management System 6.2.0, especially if the Search API endpoint is reachable from untrusted networks. The sources do not identify other affected versions or exact endpoint paths.

Exploitation context

VulDB reports that exploit material has been publicly released and that the vendor did not respond to disclosure. The CVE is not marked as CISA KEV in the supplied bundle, and no provided source confirms active exploitation in the wild.

Researcher notes

Evidence is thin beyond VulDB-style reporting. The vulnerable argument is named, but affected code, endpoint path, patch status, and exploit details are not validated in the bundle. Avoid assuming broader Das products or versions are affected.

Mitigation direction

  • Identify any Das Parking Management System 6.2.0 deployments.
  • Remove public access to the Search API where possible.
  • Restrict access to trusted management networks or VPN users.
  • Check Das or VulDB guidance for vendor fixes or mitigations.
  • Monitor application and database logs for suspicious Search API activity.
  • Plan replacement or isolation if no vendor fix becomes available.

Validation and detection

  • Confirm installed product name and version against asset inventory.
  • Determine whether the Search API is reachable from untrusted networks.
  • Review logs for unusual Value parameter use or SQL error patterns.
  • Check whether database permissions are limited for the application account.
  • Verify compensating access controls block unauthenticated remote access.
Prepared
Confidence
medium
Sources
6

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cwe · medium confidence lookup

CWE-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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2026-9552 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
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

Official CVE source material

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.

4 CVSS vectors
6 Timeline events
1 ADP providers
5 Source links

SSVC decision data

CISA-ADP CISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

4 official scores

We 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.

Score Version Severity Vector Exploit Impact Source
7.5 CVSS 2.0 High AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 10 6.4 VulDB
7.3 CVSS 3.1 High 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
7.3 CVSS 3.0 High 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
6.9 CVSS 4.0 Medium 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 Medium
CVSS 4.0 vector shape for CVE-2026-9552 Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timeline VulDB

    Advisory disclosed

  2. Source timeline VulDB

    VulDB entry created

  3. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timeline VulDB

    VulDB entry last update

  5. CVE published CVE Program

    The CVE record was published.

  6. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADP CISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

Vendor Product Version / package Status
Das Parking Management System 停车场管理系统 6.2.0 Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

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.

CWE-89 · source CWE mapping

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.