Skype For Business ServerApplication · Microsoft

CVE-2023-36786

HIGH · 7.2 CVSS v3.1 Published 2023-10-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Skype for Business Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Skype For Business ServerApplication
Affected:= 2015= 2019

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch msrc.microsoft.com →
Recommended fix Moderate confidence

Microsoft recommends migrating to Microsoft Teams as Skype for Business Server 2015 has reached end of support; for continued on-premises deployment, upgrade to the latest supported Skype for Business Server 2019 cumulative update

  1. Review the vendor patch documentation at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36786 to identify the specific update required for your Skype for Business Server version
  2. Download and install the appropriate security update for Skype for Business Server 2015 or 2019 as specified in the vendor guidance
  3. Apply the update following standard Microsoft update installation procedures for Skype for Business Server
  4. After installation, verify the update was successfully applied by checking the installed updates through Programs and Features or the Skype for Business Server Management Shell
  5. Test Skype for Business Server functionality to ensure the update did not disrupt any business-critical features
Caveat Skype for Business Server 2015 is end-of-life; upgrading may introduce compatibility changes with older clients or integrations; ensure client version compatibility before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36786 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data