dbcve.org
InjectionWeakness · CWE-74

CVE-2026-9544

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 found in Shenzhen Sixun Software Sixun Shanghui Group Business Management System 10. Affected by this vulnerability is an unknown functionality of the file /api/Dinner/PayConfig. Performing a manipulation of the argument tableno results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could 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 · moderate confidence

SQL injection vulnerability in the /api/Dinner/PayConfig endpoint of Shenzhen Sixun Software Sixun Shanghui Group Business Management System 10. The 'tableno' parameter is not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement parameterized queries or prepared statements for all database operations involving user input. Additionally, apply input validation and output encoding for the tableno parameter.

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. Identify if Sixun Shanghui Business Management System is deployed
    Review your web application inventory or scan for the application. Look for the application banner, error pages, or HTTP headers that may reveal the product name. Check the URL structure or consult your asset management system for this software.
    Affected if The Shenzhen Sixun Software Sixun Shanghui Group Business Management System is running in your environment
  2. Verify the installed version matches the affected release
    Check the application version through admin panels, about pages, or by querying the system directly. Compare your version number to the affected version 10 mentioned in the CVE summary. Some versions may display in login pages, footers, or API responses.
    Affected if The installed version is 10 (Sixun Shanghui Group Business Management System version 10)
  3. Confirm the PayConfig API endpoint is accessible
    Attempt to access the /api/Dinner/PayConfig endpoint on your server. Send an HTTP GET or POST request to this path and observe the response. Check if the endpoint responds (even with an error) versus returning a 404.
    Affected if The /api/Dinner/PayConfig endpoint exists and responds in your environment
  4. Test if the tableno parameter is accepted and processed
    Send a request to /api/Dinner/PayConfig with a tableno parameter (for example, tableno=1). Inspect whether the application processes this parameter or reflects it in the response. A functional test does not require exploiting the SQL injection, only confirming the parameter is handled.
    Affected if The tableno parameter is accepted and processed by the PayConfig endpoint

Your environment is affected if you are running Shenzhen Sixun Software Sixun Shanghui Group Business Management System version 10 and the /api/Dinner/PayConfig endpoint with the tableno parameter is accessible and functional in your deployment.

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

Implement parameterized queries or prepared statements for all database operations involving user input. Additionally, apply input validation and output encoding for the tableno parameter.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9544 — 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-9544 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