CVE-2024-49035VulnerabilityPublished 26 Nov 2024Updated 21 Oct 2025

CVE-2024-49035: Microsoft Partner Center · Improper Privilege Management

Affects Microsoft Partner CenterSource CVE Database V5

Exploited in the wild · KEV due 18 Mar 2025 · 1% EPSS : apply the vendor's fix or mitigations to Microsoft Partner Center now.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

8.7High

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

KEV deadline: 18 Mar 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 26 Nov 2024
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: evidence found.
Listed in CISA KEV 91 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Microsoft Corporation
11 Oct 202420:57 UTC, 46 days before disclosure
CVE published
on cve.org
26 Nov 202419:40 UTC, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
25 Feb 2025, 91 days after disclosure
KEV remediation due
US federal deadline
18 Mar 2025, 112 days after disclosure

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

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

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Description

An improper access control vulnerability in Partner.Microsoft.com allows an a unauthenticated attacker to elevate privileges over a network.

Impact

The impact of CVE-2024-49035 is significant for organizations relying on Microsoft Partner Center for partner management and service provisioning. Successful exploitation could allow attackers to escalate privileges without authentication, potentially leading to unauthorized access to sensitive business data, partner contracts, and administrative controls. This could result in data breaches, unauthorized changes to partner configurations, disruption of partner services, and potential lateral movement within the Microsoft ecosystem. The confidentiality and integrity of partner data are at high risk, while availability is not directly impacted. Organizations could face operational disruptions, financial losses, and reputational damage if attackers leverage this vulnerability. Additionally, because Partner Center is a cloud-based platform used globally, the scope of impact could be broad, affecting multiple partners and customers. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once patches are released or if the vulnerability is reverse-engineered.

Mitigation

To mitigate CVE-2024-49035, organizations should: 1) Monitor official Microsoft communications closely for patches or updates and apply them immediately upon release. 2) Implement strict network segmentation and access controls to limit exposure of Partner Center interfaces to only trusted networks and users. 3) Employ multi-factor authentication (MFA) and least privilege principles for all accounts interacting with Partner Center to reduce the impact of potential privilege escalation. 4) Conduct regular audits of Partner Center account permissions and activity logs to detect unusual or unauthorized access patterns. 5) Educate users and administrators about phishing and social engineering risks, as user interaction is required for exploitation. 6) Use advanced threat detection tools to monitor for anomalous behavior indicative of privilege escalation attempts. 7) Develop and rehearse incident response plans specifically addressing privilege escalation and unauthorized access scenarios within cloud partner management platforms. 8) Consider temporary restrictions or additional verification steps for critical administrative functions until patches are applied.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 21:50 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats