cve.bz

CVE-2023-21752 microsoft: Improper Access Control

7.1 highExploitEPSS 5.5%

High (7.1) in microsoft. EPSS 5.5% estimated probability of exploitation activity in the next 30 days.

On this page
Windows Backup Service Elevation of Privilege Vulnerability

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
5.5% (unchanged from 5.5% a week ago; 5.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 93rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2023-21752 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-21752?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-21752?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-21752 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.2486
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.1105
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19044.2486
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.1455
Microsoft Windows 10 Version 20H2from 10.0.0 before 10.0.19042.2486
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.3887
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.3887
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.5648
Microsoft Windows 7 Service Pack 1from 6.1.0 before 6.1.7601.26321
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.19685
Microsoft Windows 7from 6.1.0 before 6.1.7601.26321

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON