vciy

CVE-2023-24880

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Windows SmartScreen Security Feature Bypass Vulnerability

CVE-2023-248804 of 4 sources documented this
65

rank 65 = 40 + 11 + 0 + 8 + 6

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.78152 · CISA KEV listed  ·  without this subject the record ranks 25

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.4, from the CNA  ·  without this subject the record ranks 54

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 65

How much of the world it touches

NVD CPE configurations

10 products in the CPE ranges  ·  without this subject the record ranks 57

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 59

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.67Mover the next 30 days, if this record is yours
Movement+$1.01Mon 2025-11-21, the last material move, 9 months before this reading
Basisassumeda published average, not your estate

$1.67M = $4.99M incident cost x 0.42806422275080447 exposure x 0.78152 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.78152EPSSKEV · LISTED
Severity4.4 MEDIUMreceipt
Harmpartial impact · ransomware-linkedreceipt
Exploitationransomware use knownreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-11-21, 287 days at 0.78, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoft 365Google ChromeQualcomm, Inc.CVE-2021-4065524880

This record is one instance of CWE-863, incorrect authorization. The index holds 4014 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Microsoft Windows 10 Version 1809? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · no privileges required · user interaction required · low attack complexityreceipt
ImpactPartial integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-863 Incorrect Authorizationreceipt
Published consequencesCWE-863: Confidentiality: Read Application Data, Read Files or Directories; Integrity: Modify Application Data, Modify Files or Directories…[email protected]
Ransomware campaign useKnown (CISA)receipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in10.0.17763.4131; 10.0.20348.1607; 10.0.19042.2728; 10.0.22000.1696; 10.0.19044.2728; 10.0.22621.1413; 10.0.19045.2728; 10.0.14393.5786receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2023-04-04receipt
CISA required actionApply updates per vendor instructions.receipt
Published to CISA KEVsame dayderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Ransomware campaign use known, 2023-03-14.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed2023-03-14receipt
  • RUNG 4Ransomware campaign use known2023-03-14receipt

Authority who says so

CVSS, the CNA4.4 MEDIUMreceipt
Exploit probability0.78152 · top 0.44% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes61 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1809; Microsoft Windows Server 2019; Microsoft Windows Server 2019 (Server Core installation); Microsoft Windows Server 2022; Microsoft Windows 10 Version 20H2…receipt
Published rangesmicrosoft windows 10 1607 < 10.0.14393.5786; microsoft windows 10 1809 < 10.0.17763.4131; microsoft windows 10 20h2 < 10.0.19042.2728; microsoft windows 10 21h2 < 10.0.19044.2728receipt
Show all 10 published ranges
microsoft windows 10 1607 < 10.0.14393.5786
microsoft windows 10 1809 < 10.0.17763.4131
microsoft windows 10 20h2 < 10.0.19042.2728
microsoft windows 10 21h2 < 10.0.19044.2728
microsoft windows 10 22h2 < 10.0.19045.2728
microsoft windows 11 21h2 < 10.0.22000.1696
microsoft windows 11 22h2 < 10.0.22000.1413
microsoft windows server 2016 < 10.0.14393.5786
microsoft windows server 2019 < 10.0.17763.4131
microsoft windows server 2022 < 10.0.20348.1602
Fixed in10.0.17763.4131; 10.0.20348.1607; 10.0.19042.2728; 10.0.22000.1696; 10.0.19044.2728; 10.0.22621.1413; 10.0.19045.2728; 10.0.14393.5786receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Windows SmartScreen Security Feature Bypass Vulnerability receipt

NVD's analysis a second authority

weakness
CWE-863
affected versions
microsoft windows 10 1607 < 10.0.14393.5786; microsoft windows 10 1809 < 10.0.17763.4131; microsoft windows 10 20h2 < 10.0.19042.2728; and 7 more, listed in full below
also scored by
[email protected] 4.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L · [email protected] 4.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

check it yourself msrc.microsoft.com receipt

Dated events

2023-03-14Added to CISA KEV2023-04-04CISA remediation due2025-03-17EPSS moved 0.01 to 0.752025-11-21EPSS moved 0.30 to 0.77

Movement the material steps

15 Mar 20230.00404
17 Mar 20250.74707 · crossed 0.10 and 0.50 · scoring model v2025.03.14
29 Mar 20250.50023
30 Mar 20250.74707
15 Apr 20250.90812 · crossed 0.90
28 Oct 20250.83922 · crossed 0.90
18 Nov 20250.29828 · crossed 0.50
21 Nov 20250.77286 · crossed 0.50
15 Jun 20260.78005 · scoring model v2026.06.15
19 Jun 20260.78152

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 50 observations
15 Mar 20230.00404
22 Mar 20230.00304
8 May 20230.01017
16 May 20230.00858
16 Jun 20230.01075
29 Jun 20230.01125
8 Jul 20230.00317
1 Aug 20230.00313
25 Aug 20230.00420
19 Sep 20230.00496
27 Sep 20230.00440
1 Feb 20240.00696
12 Feb 20240.00550
9 Mar 20240.00791
20 Mar 20240.00450
2 Apr 20240.00499
15 Apr 20240.00636
27 Apr 20240.00518
10 May 20240.00385
5 Jun 20240.00606
1 Jul 20240.00640
15 Jul 20240.01279
28 Jul 20240.00864
11 Aug 20240.01221
24 Aug 20240.00954
4 Oct 20240.00984
17 Dec 20240.00543
25 Feb 20250.00984
26 Feb 20250.01390
17 Mar 20250.74707
29 Mar 20250.50023
30 Mar 20250.74707
15 Apr 20250.90812
13 May 20250.90535
2 Jul 20250.90812
19 Sep 20250.90883
2 Oct 20250.90812
22 Oct 20250.9036
28 Oct 20250.83922
29 Oct 20250.81429
5 Nov 20250.80507
10 Nov 20250.77286
18 Nov 20250.29828
21 Nov 20250.77286
15 Mar 20260.76892
16 Mar 20260.74734
19 Mar 20260.73308
22 May 20260.74637
15 Jun 20260.78005
19 Jun 20260.78152

50 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.78152Published · CISA KEV2023-03-14Index as of2026-09-04

Listed by CISA on the day it published, exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.29828 → 0.77286) and the record had been public for 3 years, 5 months when this index was last written.

No material movement in 77 days as of the last ingest this index recorded.

Published 2023-03-14 receipt · CISA KEV 2023-03-14 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-863, incorrect authorization. The index holds 4014 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2022-41091 · Microsoft Windows 10 Version 1507matches 8 of 9KEV listed · 2022receipt
CVE-2023-21715 · Microsoft 365 Apps for Enterprisematches 5 of 9KEV listed · 2023receipt
CVE-2021-30533 · Google Chromematches 5 of 9KEV listed · 2021receipt
CVE-2025-21479 · Qualcomm, Inc. Snapdragonmatches 4 of 9KEV listed · 2025receipt
CVE-2025-21480 · Qualcomm, Inc. Snapdragonmatches 4 of 9KEV listed · 2025receipt
CVE-2021-40655matches 3 of 8KEV listed · 2021receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

4014 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

microsoft windows 10 version 1809

Of the 5 records in this family, this is the only one holding a stated fix version: 10.0.17763.4131; 10.0.20348.1607; 10.0.19042.2728; 10.0.2200.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2023-24880.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.