dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-62209

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Insertion of sensitive information into log file in Windows License Manager allows an authorized attacker to disclose information locally.

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

Windows License Manager has a vulnerability where it writes sensitive information to log files, allowing a local authorized attacker to read this information and gain unintended access to sensitive data.

MitigationApply available Windows security updates for Windows License Manager. Review and secure log file permissions to prevent unauthorized access, and audit existing logs for any exposed sensitive information.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Check Windows version and build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full version and build number
    Affected if The build number is lower than any of the affected thresholds: 10240.21161 (1507), 14393.8519 (1607), 17763.7919 (1809), 19044.6456 (21h2), 19045.6456 (22h2), 22621.6060 (11 22h2), 22631.6060 (11 23h2), or 26100.6899 (11 24h2)
  2. Identify Windows License Manager service
    Open Services console (services.msc) or run 'sc query wlms' in Command Prompt to check if the Windows License Manager service exists
    Affected if The Windows License Manager service (wlms) is present and running on the system
  3. Locate License Manager log files
    Check common Windows log directories such as C:\Windows\Logs\, C:\ProgramData\Microsoft\WLMS\, or search for files named 'wlm*log*' using 'dir /s /b C:\*wlm*.log 2>nul'
    Affected if Log files created by Windows License Manager exist on the system
  4. Inspect log file permissions
    Right-click the identified log file, go to Properties > Security, or run 'icacls "<log_file_path>"' to view which users and groups have read access
    Affected if Users other than SYSTEM, Administrators, or the current user have Read permission to the log files
  5. Search for sensitive data in logs
    Open the identified log files with a text editor or run 'findstr /i "password token key secret" "<log_file_path>"' to search for sensitive strings
    Affected if The log files contain credentials, tokens, license keys, or other sensitive information that should not be exposed

The system is likely affected if it runs a Windows version below the patched builds AND has Windows License Manager log files with overly permissive access that expose sensitive information to non-privileged local 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.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply available Windows security updates for Windows License Manager. Review and secure log file permissions to prevent unauthorized access, and audit existing logs for any exposed sensitive information.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21161 | Windows 10 1607: 10.0.14393.8519 | Windows 10 1809: 10.0.17763.7919 | Windows 10 21h2: 10.0.19044.6456 | Windows 10 22h2: 10.0.19045.6456 | Windows 11 22h2: 10.0.22621.6060 | Windows 11 23h2: 10.0.22631.6060 | Windows 11 24h2: 10.0.26100.6899

  1. Open Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. After updates are installed, restart the computer to apply the changes
  4. Verify the installed version matches or exceeds the fixed build number for your Windows version
Caveat Standard Windows update apply risk - test mission-critical systems before broad deployment

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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