CVE-2025-62575
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 · uneditedNMIS/BioDose V22.02 and previous versions rely on a Microsoft SQL Server database. The SQL user account 'nmdbuser' and other created accounts by default have the sysadmin role. This can lead to remote code execution through the use of certain built-in stored procedures.
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 confidenceNMIS/BioDose V22.02 configures Microsoft SQL Server with database users (including 'nmdbuser') granted the sysadmin role by default. This excessive privilege allows authenticated database users to leverage built-in SQL Server stored procedures (e.g., xp_cmdshell) to execute operating system commands on the host, achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 NMIS/BioDose installation and versionLocate the NMIS or BioDose installation directory and check the version file or product information. Common locations may include /opt/nmis or the application root. Look for version indicators such as a version.txt, about screen, or the installer manifest.Affected if The installed version is below 23.0 (e.g., V22.02 or earlier)
-
Confirm Microsoft SQL Server is the database backendCheck the application configuration files for the database connection settings. Look for SQL Server-specific connection strings, JDBC/ODBC drivers configured for MS SQL, or references to MSSQL in config files.Affected if The application uses Microsoft SQL Server as its database backend
-
Check database user nmdbuser role membershipConnect to the MS SQL Server instance using SQL Server Management Studio or sqlcmd. Execute: SELECT member.name AS role_member, roles.name AS role_name FROM sys.server_role_members INNER JOIN sys.server_principals roles ON server_role_members.role_principal_id = roles.principal_id INNER JOIN sys.server_principals member ON server_role_members.member_principal_id = member.principal_id WHERE member.name = 'nmdbuser'Affected if The nmdbuser account is a member of the sysadmin server role
-
Verify xp_cmdshell is accessibleAs an authenticated database user (nmdbuser), attempt to check xp_cmdshell status: EXEC sp_configure 'xp_cmdshell' or test execution capability. This requires database user authentication to be achievable.Affected if xp_cmdshell can be enabled or executed by the nmdbuser account due to sysadmin privileges
The environment is affected if NMIS/BioDose version is below 23.0, uses Microsoft SQL Server, and the nmdbuser database account has sysadmin role membership which enables command execution via xp_cmdshell.
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 data23.0
Revoke sysadmin privileges from application database users and create least-privilege database users with only the specific database roles and permissions required for NMIS/BioDose to function properly.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62575 — 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-62575 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