dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-54319

MEDIUM · 6.3 CVSS v3.1 Published 2025-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
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).

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 confidence

WeOS 5 versions 5.24 through 5.24.4 have a vulnerability where verbose syslog logging includes credentials in log output. This allows unauthorized actors who can access the syslog data to obtain sensitive authentication credentials.

MitigationDisable verbose logging that captures credentials in syslog, or filter sensitive data from syslog streams. If available, upgrade to a patched WeOS version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/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 checks

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

  1. Identify WeOS version
    Check the system version using 'weosctl version' or inspect /etc/weos-release, or look for version information in the web interface under System > Status
    Affected if The installed version is 5.24, 5.24.1, 5.24.2, 5.24.3, or 5.24.4
  2. Check syslog configuration
    Examine /etc/syslog.conf or /etc/rsyslog.conf and any included configuration files in /etc/rsyslog.d/ for logging settings
    Affected if Verbose logging of authentication events (such as login attempts, SSH connections, or admin actions) is enabled and sent to syslog
  3. Inspect recent syslog for credentials
    Review recent syslog entries using 'tail -n 1000 /var/log/syslog' or 'journalctl -n 1000' for authentication-related logs that may contain plaintext passwords, API keys, or tokens
    Affected if Log entries contain visible credentials such as passwords, API keys, tokens, or authentication tokens in plain text
  4. Check authentication module logging level
    If available, access the WeOS administrative interface and review logging settings under System > Logging or Debug > Syslog to verify if credential verbose logging is enabled
    Affected if Authentication logging is set to verbose or debug level that captures credential data

You are affected if running WeOS 5 versions 5.24 through 5.24.4 with verbose authentication logging enabled and credentials are being written to syslog output.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable verbose logging that captures credentials in syslog, or filter sensitive data from syslog streams. If available, upgrade to a patched WeOS version.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-54319 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