CVE-2026-3200
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 was identified in z-9527 admin 1.0/2.0. The affected element is the function checkName/register/login/getUser/getUsers of the file /server/controller/user.js. The manipulation leads to sql injection. The attack can be initiated remotely. The exploit is publicly available and might 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 confidenceA SQL injection vulnerability exists in the z-9527 admin application (versions 1.0 and 2.0) within /server/controller/user.js. Multiple user-facing functions (checkName, register, login, getUser, getUsers) fail to properly sanitize user input before using it in SQL queries, allowing remote attackers to inject malicious SQL code.
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.
-
Identify the z-9527 admin application versionInspect the application's package.json, version manifest, or the main entry file for a version identifier matching 1.0 or 2.0Affected if The installed version is 1.0 or 2.0 of the z-9527 admin application
-
Locate the vulnerable user.js controllerSearch for the file at /server/controller/user.js within the application codebaseAffected if The file /server/controller/user.js exists in the application installation
-
Inspect affected functions for unsanitized SQL inputOpen user.js and review the checkName, register, login, getUser, and getUsers functions for direct string concatenation or template literals used in SQL query construction without parameterized queriesAffected if Any of these five functions use dynamic SQL query construction (e.g., 'SELECT * FROM users WHERE name = ' + username) instead of prepared statements or parameterized queries
-
Verify the application accepts user inputConfirm that the affected endpoints are exposed and accessible, typically via HTTP routes that map to these functions (e.g., /api/user/checkName, /api/user/register, /api/user/login)Affected if The application exposes HTTP endpoints that invoke the vulnerable functions with unsanitized user-supplied input
-
Check for web-facing exposureDetermine if the application server is accessible from network locations where attackers could send malicious SQL payloads through HTTP requestsAffected if The z-9527 admin application is accessible over the network without additional authentication barriers beyond the vulnerable login function
You are affected if you are running z-9527 admin application version 1.0 or 2.0 with the /server/controller/user.js file present and any of the checkName, register, login, getUser, or getUsers functions using unsanitized SQL query construction.
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 dataReplace dynamic SQL query construction with parameterized queries or prepared statements across all affected functions in user.js. Implement proper input validation and output encoding as defense-in-depth.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3200 — 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-2026-3200 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