Skip to content

CVE-2023-36563

Microsoft WordPad Information Disclosure Vulnerability

CVSS
6.5Mediumscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 10 Oct 2023CISA deadline for US federal agencies: 31 Oct 2023
EPSS
20.3%chance of exploitation in the next 30 daystop 3% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
10 Oct 2023analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable
At runtime
Attack vector
network
Weakness
  • CWE-20 Improper Input Validation
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Microsoft Windows 10 Version 1507>= 10.0.10240.0 and < 10.0.10240.20232Vendor says fixed in: not stated
Microsoft Windows 10 Version 1607>= 10.0.14393.0 and < 10.0.14393.6351Vendor says fixed in: not stated
Microsoft Windows 10 Version 1809>= 10.0.17763.0 and < 10.0.17763.4974>= 10.0.0 and < 10.0.17763.4974Vendor says fixed in: not stated
Microsoft Windows 10 Version 21H2>= 10.0.19043.0 and < 10.0.19041.3570Vendor says fixed in: not stated
Microsoft Windows 10 Version 22H2>= 10.0.19045.0 and < 10.0.19045.3570Vendor says fixed in: not stated
Microsoft Windows 11 version 21H2>= 10.0.0 and < 10.0.22000.2538Vendor says fixed in: not stated
Microsoft Windows 11 version 22H2>= 10.0.22621.0 and < 10.0.22621.2428Vendor says fixed in: not stated
Microsoft Windows Server 2008 R2 Service Pack 1>= 6.1.7601.0 and < 6.1.7601.26769Vendor says fixed in: not stated
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)>= 6.1.7601.0 and < 6.1.7601.26769Vendor says fixed in: not stated
Microsoft Windows Server 2008 Service Pack 2>= 6.0.6003.0 and < 6.0.6003.22317Vendor says fixed in: not stated
Microsoft Windows Server 2008 Service Pack 2>= 6.0.6003.0 and < 6.0.6003.22317Vendor says fixed in: not stated
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)>= 6.0.6003.0 and < 6.0.6003.22317Vendor says fixed in: not stated
Microsoft Windows Server 2012>= 6.2.9200.0 and < 6.2.9200.24523Vendor says fixed in: not stated
Microsoft Windows Server 2012 R2>= 6.3.9600.0 and < 6.3.9600.21620Vendor says fixed in: not stated
Microsoft Windows Server 2012 R2 (Server Core installation)>= 6.3.9600.0 and < 6.3.9600.21620Vendor says fixed in: not stated
Microsoft Windows Server 2012 (Server Core installation)>= 6.2.9200.0 and < 6.2.9200.24523Vendor says fixed in: not stated
Microsoft Windows Server 2016>= 10.0.14393.0 and < 10.0.14393.6351Vendor says fixed in: not stated
Microsoft Windows Server 2016 (Server Core installation)>= 10.0.14393.0 and < 10.0.14393.6351Vendor says fixed in: not stated
Microsoft Windows Server 2019>= 10.0.17763.0 and < 10.0.17763.4974Vendor says fixed in: not stated
Microsoft Windows Server 2019 (Server Core installation)>= 10.0.17763.0 and < 10.0.17763.4974Vendor says fixed in: not stated
Microsoft Windows Server 2022>= 10.0.20348.0 and < 10.0.20348.2031Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • microsoft:windows_10_1507
  • microsoft:windows_10_1607
  • microsoft:windows_10_1809
  • microsoft:windows_10_21h2
  • microsoft:windows_10_22h2
  • microsoft:windows_11_21h2
  • microsoft:windows_11_22h2
  • microsoft:windows_server_2008
  • microsoft:windows_server_2012
  • microsoft:windows_server_2016
  • microsoft:windows_server_2019
  • microsoft:windows_server_2022

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The vulnerability involves Microsoft WordPad, which is a local application. The attacker needs local access or user interaction to exploit it, so the malicious input does not come through HTTP requests that a web application firewall could inspect.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 10 Oct 2023.
CISA due date
31 Oct 2023, the remediation deadline for US federal agencies
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 23 Feb 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 10 Oct 2023Added to CISA KEV (exploited in the wild)
  2. 10 Oct 2023Published1 day later
  3. 31 Oct 2023CISA remediation due date (US federal agencies)20 days later
  4. 23 Feb 2024CISA SSVC assessment: exploitation active116 days (about 4 months) later
  5. 21 Oct 2025CVE record last updated606 days (about 2 years) later
  6. 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionRequiredA victim must click, open or otherwise cooperate.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityNoneNo unauthorised modification.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2023-36563 being exploited?

Yes. CVE-2023-36563 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-36563?

CVE-2023-36563 is rated Medium with a CVSS score of 6.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-36563?

Yes. A fix has been recorded for CVE-2023-36563. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-36563 affect?

CVE-2023-36563 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 8 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

2 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

Other links (1)

  • cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-36563

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com