dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 31 Oct 2023.
Windows 10 1507Operating system · Microsoft

CVE-2023-36563

MEDIUM · 5.5 CVSS v3.1 Developing Published 2023-10-10
Fix available
A fix is available. Upgrade to 10.0.10240.20232 / 10.0.14393.6351 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild No privileges Patch available

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
Microsoft WordPad Information Disclosure Vulnerability

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-10.

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.20232
Windows 10 1607Operating system
Affected:< 10.0.14393.6351
Windows 10 1809Operating system
Affected:< 10.0.17763.4974
Windows 10 21h2Operating system
Affected:< 10.0.19041.3570
Windows 10 22h2Operating system
Affected:< 10.0.19045.3570
Windows 11 21h2Operating system
Affected:< 10.0.22000.2538
Windows 11 22h2Operating system
Affected:< 10.0.22621.2428
Windows Server 2008Operating system
Affected:all versions= r2

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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.20232 / 10.0.14393.6351 / 10.0.17763.4974 or later
Fixed in 10.0.10240.2023210.0.14393.635110.0.17763.4974
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Apply Microsoft security updates (patch) to reach the fixed build numbers listed above - refer to Microsoft Security Bulletin for exact KB article numbers

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Settings > Windows Update > Check for updates
  3. Install all available security updates, particularly those dating from the vulnerability release month (October 2023 for this CVE)
  4. Verify the patch installed by checking the installed updates or confirming the build number meets or exceeds: 10.0.10240.20232 (Win10 1507), 10.0.14393.6351 (Win10 1607), 10.0.17763.4974 (Win10 1809), 10.0.19041.3570 (Win10 21h2), 10.0.19045.3570 (Win10 22h2), 10.0.22000.2538 (Win11 21h2), or 10.0.22621.2428 (Win11 22h2)
  5. For Windows Server 2008/R2, apply the applicable security update from Microsoft or consider upgrading as these versions are end-of-life
Caveat Standard Windows security update risks; ensure backups and test in non-production environment first on legacy systems

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get it fixed fast

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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