Password SecureApplication · Netwrix

CVE-2025-26817

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-03
Fix available
A fix is available. Upgrade to 9.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Netwrix Password Secure 9.2.0.32454 allows OS command injection.

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 confidence

Netwrix Password Secure version 9.2.0.32454 contains an OS command injection vulnerability. This allows attackers to inject and execute arbitrary operating system commands on the target host, potentially leading to complete system compromise. The critical severity (CVSS 9.8) suggests the vulnerability is exploitable remotely without authentication.

MitigationApply the vendor-provided patch or update to Netwrix Password Secure to a version that addresses this vulnerability. Until patched, consider network segmentation and restricting access to the application interface.

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
Password SecureApplication
Affected:< 9.2.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Netwrix Password Secure is installed
    Check for Netwrix Password Secure installation: look for the application in Add/Remove Programs (Windows) or check common installation directories such as C:\Program Files\Netwrix or /opt/netwrix. Also check for running services named Netwrix Password Secure.
    Affected if Netwrix Password Secure is found on the system
  2. Determine installed version
    Locate the version information: check the application's About or Help section, look for a version file in the installation directory, or query the Windows Registry under HKLM\SOFTWARE\Netwrix\Password Secure for the Version value.
    Affected if The installed version is 9.2.0.32454 or any version lower than 9.2.1
  3. Check application network exposure
    Determine if the web interface or remote access component is exposed to the network. Review firewall rules and IIS/web server configuration to see if port 8080, 443, or the application port is accessible from untrusted networks.
    Affected if The application web interface is accessible from the internet or untrusted networks without VPN
  4. Review for suspicious command execution
    Audit system logs and process creation events for unusual commands spawned by the application service account. Check Windows Event Logs (Security, Application) and any available application audit logs for unexpected system commands or script executions.
    Affected if Unexpected shell commands, PowerShell executions, or cmd.exe invocations appear in logs attributed to the Password Secure service

You are affected if Netwrix Password Secure version 9.2.0.32454 or any version below 9.2.1 is installed and the application is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 9.2.1 or later
Fixed in 9.2.1
Interim mitigation

Apply the vendor-provided patch or update to Netwrix Password Secure to a version that addresses this vulnerability. Until patched, consider network segmentation and restricting access to the application interface.

Recommended fix Moderate confidence

9.2.1

  1. Upgrade Netwrix Password Secure to version 9.2.1 or later to resolve the OS command injection vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Password Secure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26817 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26817 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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