CVE-2025-30398
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 · uneditedMissing authorization in Nuance PowerScribe allows an unauthorized attacker to disclose information over a network.
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 · moderate confidenceNuance PowerScribe, a medical dictation and transcription platform, lacks proper authorization checks on certain network endpoints or functionalities. This allows unauthenticated attackers to access sensitive information over the network without any credentials, potentially exposing patient data or system configurations.
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= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 4.0.8= 4.0.9= 2019.1= 2019.2= 2019.3= 2019.4= 2019.5= 2019.6= 2019.7= 2019.8= 2019.9= 2019.10= 2023.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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.
-
Locate PowerScribe installationSearch for Nuance PowerScribe installation directories or check installed programs list on the system. Common paths may include C:\Program Files\Nuance\ or check Windows Add/Remove Programs.Affected if PowerScribe software is found on the system
-
Identify installed versionOpen the application or check version information typically available in Help > About, or check version details in the installation directory or Windows registry under the PowerScribe entry.Affected if The version matches 4.0.1-4.0.9 for Powerscribe 360, or 2019.1-2019.10/2023.1 for Powerscribe One
-
Verify network service accessibilityIdentify ports or services used by PowerScribe (typically web-based or Windows services for remote access) and test connectivity from an external or untrusted network segment using network scanning tools.Affected if PowerScribe network services are reachable from network locations where authentication should be required
-
Test unauthenticated endpoint accessUsing a web browser or HTTP client, attempt to access common PowerScribe web endpoints without providing any credentials. Look for successful authentication bypass or access to protected resources.Affected if Sensitive information, patient data, or system configuration screens are accessible without any login credentials
If the installed PowerScribe version matches any of the affected versions (4.0.1-4.0.9 or 2019.1-2019.10/2023.1) AND network services are exposed without proper authentication enforcement, the environment is affected by this CVE.
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 dataImplement robust authorization controls on all network-accessible endpoints and verify that authentication is enforced for all sensitive operations. Coordinate with Nuance for vendor-specific patches and conduct a security assessment to identify all unprotected access points.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30398 — 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-30398 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