How severe is CVE-2023-28252?

CVE-2023-28252 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-28252?

Affected package information for CVE-2023-28252 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2023-28252?

No fixed version has been published for CVE-2023-28252 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2023-28252 actively exploited in the wild?

Yes. There are 14 known exploit references for CVE-2023-28252, including 11 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-28252?

CVE-2023-28252 has an EPSS (Exploit Prediction Scoring System) score of 60.0%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2023-28252 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-28252 (Microsoft Windows Common Log File System (CLFS) Driver Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-04-11. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-05-02. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2023-28252?

CVE-2023-28252 is classified as CWE-122 (CWE-122), Out-of-bounds Write (CWE-787). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2023-28252?

CVE-2023-28252 affects microsoft windows 10 20h2; microsoft windows 10 21h2; microsoft windows 10 22h2; microsoft windows 10 1507, and 9 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2023-28252 published, and has it been updated?

CVE-2023-28252 was published on April 11, 2023 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-04-11 — agencies required to remediate by 2023-05-02 · Ransomware

CVE-2023-28252

HIGH

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Published

Apr 11, 2023

Updated

Oct 28, 2025

Affected

0 pkgs

Patched

None yet

Exploits

14 known

EPSS Exploitation Probability

via FIRST.org ↗

60.0%probability of exploitation in next 30 days

High Risk98th percentile-1.91%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Affected Products

13 products · 15 configurations

windows 10 20h2microsoft

< 10.0.19042.2846

range

windows 10 21h2microsoft

< 10.0.19044.2846

range

windows 10 22h2microsoft

< 10.0.19045.2846

range

windows 10 1507microsoft

< 10.0.10240.19869

range

windows 10 1607microsoft

< 10.0.14393.5850

range

windows 10 1809microsoft

< 10.0.17763.4252

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.