CVE-2023-36003 [Medium] | Security Vulnerability in Windows 10 1507

CVE-2023-36003 is rated High Risk (65.8/100): CVSS Medium severity, with high exploitation likelihood (EPSS 38.57%, 97th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +6.05% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-12-30	32.51%	38.57%	+6.05%
2	2025-11-21	30.57%	32.51%	+1.94%
3	2025-11-18	—	30.57%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-12-30

32.51%

38.57%

+6.05%

2025-11-21

30.57%

32.51%

+1.94%

2025-11-18

—

30.57%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	0.8	5.9	[email protected]
7.3	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.3	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.7

3.1

MEDIUM

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

0.8

5.9

[email protected]

7.3

3.1

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.3

5.9

[email protected]

Affected software / configurations for CVE-2023-36003

Vendor	Product	Version	Raw CPE
microsoft	windows_10_1507	< 10.0.10240.20345	cpe:2.3:o:microsoft:windows_10_1507::::::::
microsoft	windows_10_1607	< 10.0.14393.6529	cpe:2.3:o:microsoft:windows_10_1607::::::::
microsoft	windows_10_1809	< 10.0.17763.5206	cpe:2.3:o:microsoft:windows_10_1809::::::::
microsoft	windows_10_21h2	< 10.0.19041.3803	cpe:2.3:o:microsoft:windows_10_21h2::::::::
microsoft	windows_10_22h2	< 10.0.19045.3803	cpe:2.3:o:microsoft:windows_10_22h2::::::::
microsoft	windows_11_21h2	< 10.0.22000.2652	cpe:2.3:o:microsoft:windows_11_21h2::::::::
microsoft	windows_11_22h2	< 10.0.22621.2861	cpe:2.3:o:microsoft:windows_11_22h2::::::::
microsoft	windows_11_23h2	< 10.0.22631.2861	cpe:2.3:o:microsoft:windows_11_23h2::::::::
microsoft	windows_server_2016	—	cpe:2.3:o:microsoft:windows_server_2016:-:::::::*
microsoft	windows_server_2019	—	cpe:2.3:o:microsoft:windows_server_2019:-:::::::*
microsoft	windows_server_2022	—	cpe:2.3:o:microsoft:windows_server_2022:-:::::::*

References for CVE-2023-36003

URL	Tags
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36003	Patch Vendor Advisory

URL

CVE-2023-36003 | XAML Diagnostics Elevation of Privilege Vulnerability

Exploit prediction scoring system (EPSS) score for CVE-2023-36003

Common vulnerability scoring system (CVSS) metrics for CVE-2023-36003

Weakness enumeration for CVE-2023-36003

Affected software / configurations for CVE-2023-36003

References for CVE-2023-36003