dbcve.org
InjectionWeakness · CWE-74

CVE-2026-9551

HIGH · 7.3 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was identified in Das Parking Management System 停车场管理系统 6.2.0. This affects the function xp_cmdshell of the file ParkingRecord/ExportParkingRecords of the component API Endpoint. The manipulation of the argument Value leads to sql injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Das Parking Management System 6.2.0 API endpoint (ParkingRecord/ExportParkingRecords) allows injection through the Value argument. The vulnerability leverages the xp_cmdshell SQL Server stored procedure, enabling remote command execution on the underlying operating system via SQL injection.

MitigationDisable xp_cmdshell on the SQL Server instance and implement parameterized queries or stored procedures with proper input validation to remediate the SQL injection. Until vendor patch is available, consider network segmentation and web application firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the ParkingRecord/ExportParkingRecords API endpoint
    Review your web application or API documentation and routing configuration to determine if the /ParkingRecord/ExportParkingRecords endpoint is exposed. Check your API gateway, reverse proxy, or application routing tables for this path.
    Affected if The endpoint exists and accepts HTTP requests on your server
  2. Verify xp_cmdshell is enabled on the SQL Server database
    Connect to the database server and run the query: SELECT value_in_use FROM sys.configurations WHERE name = 'xp_cmdshell'; or check the configuration via SQL Server Management Studio under Surface Area Configuration or via sp_configure.
    Affected if xp_cmdshell is set to value_in_use = 1 (enabled)
  3. Check database user privileges for command execution
    Query the database roles and permissions for the user account that the application uses to connect: SELECT is_srvrolemember('sysadmin') FOR YOUR_USER; or examine the login's server roles and database permissions.
    Affected if The application database user has sysadmin server role or sufficient privileges to execute xp_cmdshell
  4. Identify installed product version
    Check your application's About page, version file, or software inventory documentation. Look for version information in the application binaries, configuration files, or vendor documentation.
    Affected if The installed version matches the affected ranges provided by the vendor (if any) - otherwise, presence of the vulnerable endpoint with xp_cmdshell enabled indicates potential exposure
  5. Inspect application and database logs for suspicious requests
    Review web application logs and SQL Server error logs for requests to /ParkingRecord/ExportParkingRecords containing unusual characters in the Value parameter (quotes, semicolons, SQL keywords). Search for patterns like ', ;, exec, xp_, sp_executesql.
    Affected if Logs show injection attempts or successful exploitation attempts against the ExportParkingRecords endpoint

Your environment is affected if the ParkingRecord/ExportParkingRecords API endpoint is exposed and xp_cmdshell is enabled with a database user that has sufficient privileges to execute it.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable xp_cmdshell on the SQL Server instance and implement parameterized queries or stored procedures with proper input validation to remediate the SQL injection. Until vendor patch is available, consider network segmentation and web application firewall rules.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9551 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9551 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data