dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7727

HIGH · 7.3 CVSS v3.1 Published 2026-05-04
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 determined in Shandong Hoteam Software PDM Product Data Management System up to 8.3.9. This affects the function GetQueryMachineGridOnePageData of the file /Base/BaseService.asmx/DataService. This manipulation of the argument SortOrder causes sql injection. The attack can be initiated remotely. Upgrading to version 8.3.10 is able to mitigate this issue. You should upgrade the affected component.

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 Shandong Hoteam Software PDM Product Data Management System allows remote attackers to inject malicious SQL queries through the SortOrder parameter in the GetQueryMachineGridOnePageData function accessible via /Base/BaseService.asmx/DataService endpoint.

MitigationUpgrade the affected Hoteam PDM system to version 8.3.10 or later to remediate this SQL injection vulnerability.

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 Hoteam PDM installation
    Search for installation directories or services named 'Hoteam', 'PDM', or check web server logs for requests to 'BaseService.asmx'
    Affected if The Hoteam PDM system is present in the environment
  2. Determine PDM version
    Check the software version via the application interface, installation directory files (like version.ini or about dialog), or by querying the DataService endpoint for version information
    Affected if Installed version is lower than 8.3.10 (e.g., 8.3.9, 8.2.x, or earlier)
  3. Verify DataService endpoint exposure
    Test accessibility of the URL path /Base/BaseService.asmx/DataService by sending an HTTP request to the application's web server
    Affected if The endpoint responds and accepts SOAP/XML requests
  4. Check for SortOrder parameter handling
    Inspect HTTP traffic or application logs for requests to GetQueryMachineGridOnePageData function, particularly those containing the SortOrder parameter
    Affected if The SortOrder parameter is accepted and processed by the DataService endpoint

The environment is affected if Hoteam PDM version is below 8.3.10 and the DataService endpoint at /Base/BaseService.asmx is exposed, allowing unauthenticated injection through the SortOrder parameter in GetQueryMachineGridOnePageData.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the affected Hoteam PDM system to version 8.3.10 or later to remediate this SQL injection vulnerability.

Recommended fix High confidence

8.3.10

  1. 1. Back up the current PDM system database and configuration files before proceeding with the upgrade
  2. 2. Obtain the version 8.3.10 upgrade package from the official Shandong Hoteam Software source (en.hoteamsoft.com)
  3. 3. Stop the PDM application services to prevent data corruption during the upgrade process
  4. 4. Install or apply the version 8.3.10 upgrade to the PDM Product Data Management System
  5. 5. Restart the PDM application services
  6. 6. Verify that the /Base/BaseService.asmx/DataService endpoint is functioning correctly and that SQL injection is no longer present by testing the GetQueryMachineGridOnePageData function with the SortOrder parameter

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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