dbcve.org
InjectionWeakness · CWE-74

CVE-2025-1797

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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, which was classified as critical, has been found in Hunan Zhonghe Baiyi Information Technology Baiyiyun Asset Management and Operations System up to 20250217. Affected by this issue is some unknown functionality of the file /wuser/anyUserBoundHouse.php. The manipulation of the argument huid leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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 the Baiyiyun Asset Management and Operations System allows remote attackers to inject malicious SQL queries via the 'huid' parameter in /wuser/anyUserBoundHouse.php. The vulnerability stems from unsanitized user input being directly used in database queries.

MitigationImplement parameterized queries or prepared statements for all database operations involving user-supplied input. Additionally, apply input validation and output encoding for the huid 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 Baiyiyun Asset Management System installation
    Check for the presence of the Baiyiyun system by searching for its web application files, typically found in web server document roots. Look for application directories containing 'asset', 'baiyiyun', or similar naming conventions.
    Affected if The Baiyiyun Asset Management and Operations System is installed on the server.
  2. Locate the vulnerable PHP file
    Search for the file /wuser/anyUserBoundHouse.php within the web application directory structure. This file handles user-bound house operations.
    Affected if The file /wuser/anyUserBoundHouse.php exists in the web application.
  3. Verify the huid parameter acceptance
    Examine the PHP file for the presence of the 'huid' parameter handling. Check if the application accepts this parameter without proper sanitization in the code.
    Affected if The application accepts a 'huid' parameter in requests to anyUserBoundHouse.php.
  4. Check network accessibility of the vulnerable endpoint
    Determine if the /wuser/anyUserBoundHouse.php endpoint is accessible from external networks or the internet. This is a remote SQL injection, so network exposure is required for exploitation.
    Affected if The endpoint is accessible from the network without authentication restrictions.
  5. Compare installed version against known affected versions
    If version information is available (check application headers, about pages, or version files), compare it against any known version ranges for this product. Without specific version data, treat all installations as potentially affected.
    Affected if The installed version falls within an affected range or cannot be determined.

The environment is affected if the Baiyiyun Asset Management System is installed with the /wuser/anyUserBoundHouse.php endpoint accessible over the network and the application accepts the 'huid' parameter without proper SQL sanitization.

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-supplied input. Additionally, apply input validation and output encoding for the huid parameter.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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