dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-41690

HIGH · 7.4 CVSS v3.1 Published 2025-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated

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
A low-privileged attacker in bluetooth range may be able to access the password of a higher-privilege user (Maintenance) by viewing the device’s event log. This vulnerability could allow the Operator to authenticate as the Maintenance user, thereby gaining unauthorized access to sensitive configuration settings and the ability to modify device parameters.

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

A privilege escalation vulnerability exists where a low-privileged Operator user can view the device's event log and retrieve the plaintext password of a higher-privilege Maintenance user. This information disclosure allows the attacker to authenticate as Maintenance, gaining unauthorized access to sensitive configuration settings and the ability to modify device parameters.

MitigationImplement proper event log sanitization to exclude sensitive data such as passwords from being logged. Additionally, enforce strict access controls on event log viewing to prevent lower-privileged users from accessing logs containing higher-privilege user credentials.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:R/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. Identify your product and version
    Locate the product name and version number in the device management interface, system information page, or firmware metadata. Consult vendor documentation if the version is not immediately visible in the UI.
    Affected if The installed version falls within any affected version range provided by the vendor for this CVE.
  2. Determine event log access privileges
    Review the user role configuration or access control matrix to confirm whether the Operator role is permitted to view system event logs. This may be found in user management, role permissions, or access control settings.
    Affected if Operator-level users are granted permission to access or view the event log functionality.
  3. Inspect event log contents for sensitive data
    As an Operator user, access the event log viewer function and search through recent log entries. Look for any instances where user credentials, passwords, or authentication tokens appear in plain text within the log records.
    Affected if The event log contains plaintext passwords or other credential information for Maintenance or administrative users.
  4. Verify if password data is logged during authentication events
    Enable verbose logging or review the current logging configuration to identify whether authentication events, user login attempts, or account changes are recorded with full credential details. Check log retention settings and data sanitization options.
    Affected if Authentication events or user account operations are logged with plaintext password data visible in the output.
  5. Test cross-privilege log access
    Log in with a low-privilege Operator account and attempt to retrieve or export event log data. Note whether the system permits retrieval of logs that may contain credentials from higher-privilege Maintenance or administrator accounts.
    Affected if Operator users can successfully view or export logs containing credentials belonging to Maintenance users.

Your environment is affected if your installed version matches the affected range and low-privilege Operator users can access event logs containing plaintext credentials of higher-privilege Maintenance users.

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

Implement proper event log sanitization to exclude sensitive data such as passwords from being logged. Additionally, enforce strict access controls on event log viewing to prevent lower-privileged users from accessing logs containing higher-privilege user credentials.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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