CVE-2023-21752
LPE in Microsoft Windows 10 1607 … 22h2
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-21752 is a high-severity Improper Access Control (CWE-284) vulnerability in Microsoft Windows 10. Its CVSS base score is 7.1 (High).
Operationally, ranked in the top 7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-21752 is an elevation of privilege vulnerability in the Windows Backup Service. It carries a CVSS 3.1 base score of 7.1 with the vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H and is associated with CWE-284. The flaw was publicly disclosed on 10 January 2023.
A local attacker who already possesses a low-privileged account on an affected Windows system can exploit the vulnerability to obtain elevated integrity and availability impact without user interaction. Successful exploitation allows the attacker to modify or disrupt backup-related operations on the host.
Microsoft has published official advisories for the issue at the listed MSRC update-guide URLs, which serve as the authoritative source for patch availability and mitigation guidance.
EPSS for the CVE rose from lower values to a peak of 0.6085 on 23 February 2026 before receding to the current score of 0.3793, indicating a period of increased exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25919
Vulnerability Data
Windows Backup Service Elevation of Privilege Vulnerability
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
The access control policy and procedures directly mandate and enforce proper access control mechanisms across the organization.
Device lock enforces restricted access until re-authentication, directly reducing unauthorized use of active sessions.
Supervision and review of access control activities directly detects and remediates improper access configurations or usages.
Explicitly identifying and documenting actions permitted without identification or authentication enforces proper access control boundaries by defining justified exceptions.
By automatically labeling outputs with security attributes, the control supports attribute-based enforcement and reduces exploitability of improper access control weaknesses.
Associating and retaining security attributes with data directly supports enforcement of access control decisions across storage, processing, and transmission.
Requiring prior authorization for each remote access type prevents improper access control over remote connections.
Requiring authorization of wireless access before allowing connections enforces proper access control for this access method.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing explicitly validates authentication, access restriction, and cryptography functions, directly catching missing or incorrect access control checks before code reaches production.
A.8.3 is the direct access-restriction control and, well implemented, blocks exploitation of most CWE-284 instances by enforcing per-identity/per-data access rules, isolation, and dynamic access management; the remainder is enforcement errors in the product's own code where A.8.3's policy is correct but the application fails to enforce it.
Ongoing audits and performance reviews of suppliers detect and correct situations where access controls or privilege assignments are weaker than contractually required, limiting an attacker's ability to exploit improper access control in the supplier's environment.
Formal incident containment and post-incident root-cause analysis reduce the window during which improper access control flaws can be exploited and ensure discovered authorization weaknesses are corrected.
Periodic independent assessment of whether documented security objectives and controls are actually implemented and effective can surface missing or bypassed access-control decisions before they are exploited.
Periodic compliance reviews and corrective-action tracking detect and close gaps where access-control rules are not enforced, reducing the window in which improper access control can be exploited.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.