Skip to content
Server Security Center
KEVmedium5.3

CVE-2023-41763: Microsoft Skype for Business Privilege Escalation

Microsoft Skype for Business · listed in the CISA catalog of actively exploited vulnerabilities since 2023-10-10.

CVSS v3.1 (CVE record)
5.3
medium
EPSS (exploit probability, 30 days)
90%
higher than 99.8% of all CVEs
Added to CISA KEV
2023-10-10
US federal due date 2023-10-31
Automatable (CISA SSVC)
yes
technical impact: partial

CVE-2023-41763 explained

CVE-2023-41763 is a privilege escalation vulnerability in Microsoft Skype for Business Server, classified as server-side request forgery (CWE-918). It affects Skype for Business Server 2015 CU13 and 2019 CU7. CISA lists it as known to be exploited, so affected servers should be updated promptly.

Impact

An unauthenticated attacker can exploit the flaw over the network with low complexity and no user interaction. The CVSS vector shows a limited confidentiality impact and no integrity or availability impact. CISA rates it automatable, meaning attackers can exploit it at scale without manual steps, with partial technical impact. Attackers are known to use this vulnerability. Whether it has been used in ransomware campaigns is unknown.

Who is affected

The CVE record lists Microsoft Skype for Business Server 2015 CU13 before 6.0.9319.869, fixed in 6.0.9319.869. It also lists Microsoft Skype for Business Server 2019 CU7 before 7.0.246.530, fixed in 7.0.246.530.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Skype for Business contains an unspecified vulnerability that allows for privilege escalation.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Skype for Business Server 2015 CU13
    Affected
    • < 6.0.9319.869
    Fixed in
    • 6.0.9319.869
  • Microsoft Skype for Business Server 2019 CU7
    Affected
    • < 7.0.246.530
    Fixed in
    • 7.0.246.530

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Skype for Business Server 2015 CU13: 6.0.9319.869
    • Microsoft Skype for Business Server 2019 CU7: 7.0.246.530
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2023-41763
  • CISA's deadline for US federal agencies: 2023-10-31 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Update Skype for Business Server 2015 CU13 to 6.0.9319.869 or later.
  2. Update Skype for Business Server 2019 CU7 to 7.0.246.530 or later.
  3. Follow Microsoft's advisory and apply any mitigations it describes.
  4. Limit network exposure of Skype for Business servers to trusted networks where possible.
  5. Check servers for signs of compromise, since the vulnerability is known to be exploited.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Partial – limited control or information

Weakness: CWE-918 Server-Side Request Forgery (SSRF)

Questions about CVE-2023-41763

Is CVE-2023-41763 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-10-10, with a US federal due date of 2023-10-31. Whether it has been used in ransomware campaigns is unknown.
Does an attacker need credentials?
No. According to the CVSS vector, the attack works over the network without privileges or user interaction.
Which versions fix the issue?
Skype for Business Server 2015 CU13 is fixed in 6.0.9319.869. Skype for Business Server 2019 CU7 is fixed in 7.0.246.530.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.