CVE-2025-53762VulnerabilityPublished 18 Jul 2025Updated 26 Feb 2026

CVE-2025-53762: Microsoft Purview · Permissive List of Allowed Inputs

Affects Microsoft PurviewSource CVE Database V5

Not known to be exploited · CVSS 8.7 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N/E:U/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-53762 effectively, organizations should: 1) Immediately review and tighten input validation rules within Microsoft Purview configurations, ensuring only strictly necessary inputs are allowed. 2) Implement the principle of least privilege by auditing and minimizing user privileges to reduce the attack surface for privilege escalation. 3) Monitor logs and alerts for unusual privilege escalation attempts or anomalous behavior within Purview environments. 4) Apply network segmentation to limit access to Purview services only to trusted and necessary network segments. 5) Stay informed on Microsoft security advisories and apply patches or updates promptly once released. 6) Conduct regular security assessments and penetration testing focused on input validation and privilege management in Purview. 7) Employ multi-factor authentication (MFA) for all users with elevated privileges to add an additional security layer. 8) Consider deploying Web Application Firewalls (WAF) or input filtering mechanisms to detect and block malicious input patterns. These steps go beyond generic advice by focusing on input validation tightening, privilege auditing, and proactive monitoring specific to the nature of this vulnerability.

Description

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

Impact

The impact of CVE-2025-53762 is substantial for organizations using Microsoft Purview. Successful exploitation allows an attacker with existing privileges to escalate their access rights, potentially gaining administrative control over Purview environments. This can lead to unauthorized access to sensitive data, manipulation of compliance policies, and disruption of data governance processes. The confidentiality and integrity of organizational data are at high risk, as attackers could exfiltrate or alter critical information. Although availability is not directly impacted, the broader consequences of privilege escalation can indirectly affect system stability and trustworthiness. Organizations in regulated industries such as finance, healthcare, and government, which rely heavily on Purview for compliance and data protection, face increased risk of regulatory violations and reputational damage. The network-based attack vector and lack of required user interaction increase the likelihood of exploitation, especially in environments with insufficient network segmentation or weak privilege management. The absence of known exploits in the wild provides a window for proactive mitigation, but the high CVSS score underscores the urgency.

CWE-183Permissive List of Allowed Inputs (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Double Encoding (opens in a new tab)
Using Leading 'Ghost' Character Sequences to Bypass Input Filters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
Using Unicode Encoding to Bypass Validation Logic (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53762 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 03:23 UTC

WeaknessesCWE-183

Technical details

References

Community reviews

Related threats