basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2024-49035
CVE-2024-49035 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-253EPSS 0.01339 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
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
Affected: Microsoft, Partner Center. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-269 Improper Privilege Management — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-269 · Improper Privilege ManagementAuthorization / access control
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 5 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.