CVE-2025-61940
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 common SQL Server user account to access data in the database. User access in the client application is restricted by a password authentication check in the client software but the underlying database connection always has access. The latest version of NMIS/BioDose introduces an option to use Windows user authentication with the database, which would restrict this database connection.
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 versions V22.02 and prior use a shared SQL Server credential for all database connections, bypassing the client application's password-based authentication. Anyone with direct database access gains full data access regardless of client-side access controls. The latest version adds Windows Authentication support to replace the shared database account.
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 installed NMIS/BioDose versionCheck the application version reported in the software itself, or look for version information in installation directories, configuration files, or the Windows Programs and Features list. Common locations include the application installation folder or any version.txt/readme file.Affected if The installed version is V22.02 or prior, or any version shown as < 23.0
-
Locate database connection configurationFind the database configuration file used by NMIS/BioDose to connect to SQL Server. This is typically in the application config directory or where connection strings are stored. Look for files containing SQL Server connection parameters.Affected if The configuration file exists and contains database connection settings for SQL Server
-
Check if Windows Authentication is configuredInspect the database connection configuration for the authentication method. Windows Authentication is typically indicated by 'Integrated Security=True', 'Integrated Security=SSPI', or similar settings. If instead you see explicit username/password fields (like 'User ID=' or 'Password=') in the connection string, shared credentials are in use.Affected if The database connection uses explicit username/password credentials rather than Windows Authentication (Integrated Security) - this indicates the vulnerable shared credential configuration
-
Verify SQL Server login in useIf you have database access, examine what login the application uses to connect to SQL Server. Check if the same database user/account is used across all installations rather than per-user Windows Authentication.Affected if All application users connect using the same shared SQL Server account rather than individual Windows-authenticated accounts
You are affected if the installed NMIS/BioDose version is below 23.0 AND the database connection relies on shared SQL Server credentials instead of Windows Authentication.
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
Upgrade to the latest NMIS/BioDose version and enable Windows Authentication for database connections to enforce proper user-level access controls.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61940 — 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-61940 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