Threats / Microsoft / CVE-2024-49035
CVE-2024-49035
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Partner Center vulnerability
Microsoft Partner Center contains an improper access control vulnerability allowing privilege escalation. The vulnerability has been exploited in the wild.
Verdict
Today item — known-exploited.
An attacker can escalate privileges within Partner Center through improper access control mechanisms. This vulnerability poses a direct risk to partner account integrity and has demonstrated active exploitation.
CISA KEV Yes · 2025-02-255EPSS 0.01339 (verify live)6CVSS 8.73CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-02-25).
Probability (EPSS)
EPSS 0.01339 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.7 (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) · Affected: Microsoft, Partner Center. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-269 Improper Privilege Management — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 91 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a Partner Center user account with limited permissions.
Business
Partner organizations face unauthorized access to restricted administrative functions and sensitive partner data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit improper access control to escalate my privileges beyond my assigned role.
Business
Attackers gain ability to modify partner agreements, access financial records, or manipulate customer relationships at scale.
3
Lateral reach — past segmentation narrative 3
Attacker
I use elevated privileges to access or modify partner and customer information across the platform.
Business
Microsoft and its partners face potential data breaches, compliance violations, and erosion of trust in the partner ecosystem.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05