Cyber Resilience

CVE-2025-53762

Microsoft Purview

Published
18 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 8.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
EPSS Score 0.0074 51th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2025-53762 is a high-severity Permissive List of Allowed Inputs (CWE-183) vulnerability in Microsoft Purview. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Microsoft Purview contains a permissive list of allowed inputs tracked as CWE-183 that produces the vulnerability described in CVE-2025-53762. The flaw permits an authorized attacker to elevate privileges across a network and carries a CVSS 3.1 base score of 8.7 reflecting network attack vector, low complexity, high-privilege requirement, and changed scope with high impact to confidentiality and integrity.

An attacker already holding high privileges can send crafted inputs over the network to expand access beyond the intended authorization boundary, achieving broad control over affected Purview resources without user interaction.

Microsoft publishes mitigation guidance and patch information for this issue in its Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53762. The associated EPSS score remains low, moving only from 0.0178 to a peak of 0.0189.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Permissive list of allowed inputs in Microsoft Purview allows an authorized attacker to elevate privileges over a network.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-21385Same product: Microsoft Purview
CVE-2021-26855Same vendor: Microsoft
CVE-2024-29053Same vendor: Microsoft
CVE-2022-41040Same vendor: Microsoft
CVE-2023-41763Same vendor: Microsoft
CVE-2024-21323Same vendor: Microsoft
CVE-2023-32052Same vendor: Microsoft
CVE-2024-21381Same vendor: Microsoft
CVE-2004-0847Same vendor: Microsoft
CVE-2021-40444Same vendor: Microsoft

Affected Assets

microsoft
purview
all versions

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V4.4.2

Mitigating Controls (NIST 800-53 r5) AI

Strict validity checks on inputs directly stop overly permissive allow lists from being used as the protection mechanism.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require rigorous allow-list design and testing that prevents permissive input validation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect overly broad allow-lists, but does not inherently prevent their creation.

prevents

Application security requirements can mandate strict, minimal allow-lists and input validation rules that prevent overly permissive lists.

prevents

Secure system architecture and engineering principles require explicit, least-privilege input validation designs that directly address permissive allow-lists.

prevents

Secure coding standards enforce rigorous input validation and reject unsafe values, mitigating permissive allow-list weaknesses.

none

Configuration management can enforce validated input rules, yet does not directly address the design flaw of permissive lists.

References