CVE-2023-24880

Windows SmartScreen Security Feature Bypass Vulnerability

MEDIUM
4.4
CVSS Score
Published: March 14, 2023 at 04:55 PM UTC
Updated: June 17, 2026 at 05:40 AM UTC
10 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows 10 1809

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.4
Exploitation
CISA KEV
Exploit prediction
EPSS 78%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score78.0%

EPSS (Exploit Prediction Scoring System) estimates a 78.0% chance this CVE is exploited in the wild within the next 30 days — higher than 100% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Windows SmartScreen contains a security feature bypass vulnerability that could allow an attacker to evade Mark of the Web (MOTW) defenses via a specially crafted malicious file.

Required Action
Apply updates per vendor instructions.
Ransomware Use
Known
Added to KEV
Mar 14, 2023
Remediation Due
Apr 4, 2023
1304 days overdue

Description

Windows SmartScreen Security Feature Bypass Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.14393.578610.0.14393.0 ≤ v < 10.0.14393.578610.0.14393.0
Affected range stops below 10.0.14393.5786, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.413110.0.0 ≤ v < 10.0.17763.413110.0.17763.0 ≤ v < 10.0.17763.413110.0.010.0.17763.0
Affected range stops below 10.0.17763.4131, so it looks safe — our inference, not a vendor statement
v < 10.0.19042.272810.0.0 ≤ v < 10.0.19042.272810.0.0
Affected range stops below 10.0.19042.2728, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.272810.0.19043.0 ≤ v < 10.0.19044.272810.0.19043.0
Affected range stops below 10.0.19044.2728, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.272810.0.19045.0 ≤ v < 10.0.19045.272810.0.19045.0
Affected range stops below 10.0.19045.2728, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.169610.0.0 ≤ v < 10.0.22000.169610.0.0
Affected range stops below 10.0.22000.1696, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.141310.0.22621.0 ≤ v < 10.0.22621.141310.0.22621.0
Affected range stops below 10.0.22000.1413, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.22621.1413, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.578610.0.14393.0 ≤ v < 10.0.14393.578610.0.14393.0
Affected range stops below 10.0.14393.5786, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.413110.0.17763.0 ≤ v < 10.0.17763.413110.0.17763.0
Affected range stops below 10.0.17763.4131, so it looks safe — our inference, not a vendor statement
v < 10.0.20348.160210.0.20348.0 ≤ v < 10.0.20348.160710.0.20348.0
Affected range stops below 10.0.20348.1607, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.4MEDIUMmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-863

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card