CVE-2025-54394VulnerabilityPublished 7 Aug 2025

CVE-2025-54394: n/a

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 11.1.25162.02 : update affected systems when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.1.25162.02

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should prioritize upgrading Netwrix Directory Manager to version 11.1.25162.02 or later, where this vulnerability is addressed. In the absence of an immediate patch, network administrators should restrict and monitor network traffic to and from Netwrix Directory Manager, especially connections involving remote Excel resources. Implementing network segmentation and enforcing strict access controls can limit exposure. Additionally, organizations should audit and rotate credentials used by Netwrix Directory Manager for remote Excel connections to reduce the risk of credential reuse. Employing encryption for data in transit, such as enforcing TLS for all communications, can help protect credentials from interception. Monitoring logs for unusual access patterns or failed authentication attempts related to Excel resource requests is also recommended. Finally, organizations should conduct regular security assessments and penetration tests focusing on identity management systems to detect potential exploitation attempts early.

Description

Netwrix Directory Manager (formerly Imanami GroupID) 11.0.0.0 before 11.1.25162.02 has Insufficiently Protected Credentials for requests to remote Excel resources.

Impact

For European organizations, this vulnerability poses a considerable risk, especially for those relying on Netwrix Directory Manager for identity and access management. Exposure of credentials used in remote Excel resource requests could lead to unauthorized access to sensitive business data, including financial, HR, or operational information stored or processed via Excel files linked remotely. This could result in data breaches, compliance violations (notably GDPR), and operational disruptions. Given the role of Netwrix Directory Manager in managing directory services, attackers could leverage stolen credentials to escalate privileges, compromise additional systems, or exfiltrate data. The impact is heightened in sectors with strict regulatory requirements such as finance, healthcare, and government institutions prevalent across Europe. Additionally, the vulnerability could undermine trust in IT infrastructure security and lead to costly incident response and remediation efforts.

References

community.netwrix.com/t/adv-2025-015-critical-vulnerabilities-in-netwrix-directory-manager-formerly-imanami-groupid-v11/17192 (opens in a new tab)

Community reviews

Loading reviews…