Skip to main content
VulnerabilityPublished Updated

CVE-2025-54319: Westermo WeOS · Sensitive Data in Logs

Affects Westermo WeOSSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Westermo WeOSAffected
  • =5.24.0
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should take the following specific actions: 1) Immediately review and adjust syslog verbosity settings on affected Westermo WeOS devices to disable verbose logging that includes sensitive credentials. 2) Apply any available patches or firmware updates from Westermo as soon as they are released; if no patches are currently available, engage with Westermo support for mitigation guidance. 3) Implement strict access controls and network segmentation to limit access to management interfaces and log files, ensuring only authorized personnel can view logs. 4) Employ secure log management practices, including encrypting log data at rest and in transit, and regularly auditing logs for sensitive information exposure. 5) Monitor network traffic for unusual access patterns that could indicate attempts to exploit this vulnerability. 6) Incorporate this vulnerability into incident response plans, preparing for potential credential compromise scenarios. 7) Conduct regular security training for operational technology (OT) personnel to recognize and respond to such vulnerabilities. These steps go beyond generic advice by focusing on configuration changes, access control, and operational security tailored to industrial network environments.

Description

An issue was discovered in Westermo WeOS 5 (5.24 through 5.24.4). A threat actor potentially can gain unauthorized access to sensitive information via system logging information (syslog verbose logging that includes credentials).

References

Community reviews

Loading reviews…