CVE-2025-1464
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 · uneditedA vulnerability, which was classified as critical, has been found in Baiyi Cloud Asset Management System up to 20250204. This issue affects some unknown processing of the file /wuser/admin.house.collect.php. The manipulation of the argument project_id leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may 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 confidenceSQL injection vulnerability in Baiyi Cloud Asset Management System (up to 20250204) in the /wuser/admin.house.collect.php file via the project_id parameter allows remote attackers to execute arbitrary SQL commands.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Baiyi Cloud Asset Management System installationLocate the application installation directory and identify if it is Baiyi Cloud Asset Management System. Check for characteristic files or headers, or access the application's main page to verify the product name.Affected if The system is confirmed to be Baiyi Cloud Asset Management System.
-
Check the application versionLocate the version file, about page, or admin panel that displays the current software version. Compare the installed version against '20250204' - any version up to and including 20250204 is affected.Affected if The installed version is 20250204 or earlier.
-
Verify the vulnerable file existsCheck if the file /wuser/admin.house.collect.php exists in the web root or application directory.Affected if The file exists and the version is 20250204 or earlier.
-
Confirm the vulnerable endpoint is accessibleTest access to the URI containing /wuser/admin.house.collect.php via HTTP/HTTPS. Verify the endpoint responds to requests.Affected if The endpoint is reachable and the version is 20250204 or earlier.
-
Check for parameter usage in the affected componentInspect the application flow that invokes admin.house.collect.php. Determine if the project_id parameter is processed without parameterized queries or input validation.Affected if The project_id parameter is used in SQL queries without prepared statements or sanitization, and the version is 20250204 or earlier.
The environment is affected if Baiyi Cloud Asset Management System version 20250204 or earlier is installed and the /wuser/admin.house.collect.php file is accessible with the project_id parameter vulnerable to unsanitized SQL input.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediate mitigation requires either parameterized queries/prepared statements or input validation/sanitization on the project_id parameter. Since public exploits exist, disable or restrict access to this endpoint until patched.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1464 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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