dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-34162

CRITICAL · 9.3 CVSS v4.0 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
An unauthenticated SQL injection vulnerability exists in the GetLyfsByParams endpoint of Bian Que Feijiu Intelligent Emergency and Quality Control System, accessible via the /AppService/BQMedical/WebServiceForFirstaidApp.asmx interface. The backend fails to properly sanitize user-supplied input in the strOpid parameter, allowing attackers to inject arbitrary SQL statements. This can lead to data exfiltration, authentication bypass, and potentially remote code execution, depending on backend configuration. The vulnerability is presumed to affect builds released prior to June 2025 and is remediated in newer versions of the product, though the exact affected range remains undefined. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-07-23 UTC.

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

An unauthenticated SQL injection vulnerability exists in the GetLyfsByParams endpoint of the Bian Que Feijiu Intelligent Emergency and Quality Control System. The strOpid parameter in the /AppService/BQMedical/WebServiceForFirstaidApp.asmx web service fails to sanitize user input, allowing attackers to inject arbitrary SQL statements without authentication.

MitigationOrganizations should immediately identify and upgrade all instances to versions released after June 2025. As an interim control, implement web application firewall rules or input validation on the affected endpoint, and restrict external access to the WebService interface until patching is complete.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm the WebServiceForFirstaidApp.asmx is exposed
    Access the URL path /AppService/BQMedical/WebServiceForFirstaidApp.asmx via HTTP/HTTPS and verify the service returns a response or WSDL definition
    Affected if The endpoint is accessible and responds without authentication, indicating the service is running
  2. Identify the installed version of the Bian Que Feijiu system
    Check system documentation, banners, or configuration files for the software version. Compare the installed version against any releases published before June 2025
    Affected if The installed version predates the June 2025 patch release and falls within the affected version range
  3. Verify the GetLyfsByParams method is available
    Inspect the WSDL or service discovery response at the asmx endpoint to confirm the GetLyfsByParams operation is listed
    Affected if The GetLyfsByParams method is present in the service definition
  4. Confirm the strOpid parameter is processed by the endpoint
    Review the application configuration files or proxy/WSDL definitions to confirm the GetLyfsByParams method accepts a strOpid parameter
    Affected if The method accepts strOpid as an input parameter without documented input validation or sanitization routines

If the Bian Que Feijiu Intelligent Emergency and Quality Control System is running a version released before June 2025, the WebServiceForFirstaidApp.asmx endpoint is exposed, and the GetLyfsByParams method with the strOpid parameter is accessible without authentication, the environment is affected by CVE-2025-34162.

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

Organizations should immediately identify and upgrade all instances to versions released after June 2025. As an interim control, implement web application firewall rules or input validation on the affected endpoint, and restrict external access to the WebService interface until patching is complete.

Recommended fix Moderate confidence

Contact vendor for latest patched version (builds post-June 2025)

  1. 1. Contact Bian Que (the vendor) to obtain the latest patched version of the Feijiu Intelligent Emergency and Quality Control System
  2. 2. Request specific version information and release notes confirming the SQL injection fix for the GetLyfsByParams endpoint
  3. 3. Before deploying in production, test the upgrade in a staging environment to verify the strOpid parameter is now properly sanitized
  4. 4. After upgrading, verify the WebServiceForFirstaidApp.asmx interface no longer accepts SQL injection payloads in the strOpid parameter
  5. 5. Implement input validation and parameterized queries as a defense-in-depth measure if not already in place

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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