Skype for Business Elevation of Privilege Vulnerability
CVE-2023-41763
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-10-10), indicating real-world exploitation has been confirmed by US federal agencies. a secondary CVSS source baseline 5.3 retained for reference (NVD's own analysis pending). Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 9.0(high)
- EG Risk
- 96(Attend)EG Risk 96/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 99.8%
- KEV
- ⚠ Exploited
Published
October 10, 2023
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jun 13, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-41763Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-41763Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 81× in last 7d / 383× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 728 total refreshes for this CVE.
- 2026-07-23 02:26 UTCEG score recompute
- 2026-07-22 22:52 UTCEG score recompute
- 2026-07-22 22:52 UTCVendor advisory
- 2026-07-22 22:52 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:06 UTCGHSA enrichment
- 2026-07-22 15:18 UTCEG score recompute
- 2026-07-22 15:18 UTCVendor advisory
- 2026-07-22 15:18 UTCGHSA enrichment
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 11:31 UTCVendor advisory
- 2026-07-22 11:31 UTCGHSA enrichment
- 2026-07-22 07:44 UTCVendor advisory
- 2026-07-22 07:44 UTCGHSA enrichment
- 2026-07-22 03:59 UTCVendor advisory
- 2026-07-22 03:59 UTCGHSA enrichment
- 2026-07-22 00:12 UTCVendor advisory
- 2026-07-22 00:11 UTCGHSA enrichment
- 2026-07-21 20:25 UTCVendor advisory
- 2026-07-21 20:25 UTCGHSA enrichment
- 2026-07-21 16:39 UTCEG score recompute
- 2026-07-21 16:39 UTCVendor advisory
- 2026-07-21 16:39 UTCGHSA enrichment
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:52 UTCVendor advisory
- 2026-07-21 12:52 UTCGHSA enrichment
- 2026-07-21 09:02 UTCVendor advisory
- 2026-07-21 09:02 UTCGHSA enrichment
- 2026-07-21 05:15 UTCVendor advisory
- 2026-07-21 05:15 UTCGHSA enrichment
- 2026-07-21 01:28 UTCVendor advisory
- 2026-07-21 01:28 UTCGHSA enrichment
- 2026-07-20 21:42 UTCVendor advisory
- 2026-07-20 21:42 UTCGHSA enrichment
- 2026-07-20 17:56 UTCEG score recompute
- 2026-07-20 17:56 UTCVendor advisory
- 2026-07-20 17:55 UTCGHSA enrichment
- 2026-07-20 17:06 UTCEPSS rescore
- 2026-07-20 14:10 UTCGHSA enrichment
- 2026-07-20 10:25 UTCGHSA enrichment
- 2026-07-20 06:40 UTCVendor advisory
- 2026-07-20 06:40 UTCGHSA enrichment
- 2026-07-20 02:42 UTCVendor advisory
- 2026-07-20 02:42 UTCGHSA enrichment
- 2026-07-19 22:56 UTCVendor advisory
- 2026-07-19 22:56 UTCGHSA enrichment
- 2026-07-19 19:10 UTCVendor advisory
- 2026-07-19 19:10 UTCGHSA enrichment
- 2026-07-19 15:25 UTCVendor advisory
- 2026-07-19 15:25 UTCGHSA enrichment
- 2026-07-19 11:40 UTCVendor advisory
- 2026-07-19 11:40 UTCGHSA enrichment
- 2026-07-19 07:54 UTCVendor advisory
- 2026-07-19 07:54 UTCGHSA enrichment
- 2026-07-19 04:08 UTCVendor advisory
- 2026-07-19 04:08 UTCGHSA enrichment
- 2026-07-19 00:22 UTCGHSA enrichment
- 2026-07-18 20:37 UTCVendor advisory
- 2026-07-18 20:37 UTCGHSA enrichment
- 2026-07-18 16:51 UTCVendor advisory
- 2026-07-18 16:51 UTCGHSA enrichment
- 2026-07-18 13:06 UTCVendor advisory
- 2026-07-18 13:06 UTCGHSA enrichment
- 2026-07-18 09:19 UTCVendor advisory
- 2026-07-18 09:19 UTCGHSA enrichment
- 2026-07-18 05:34 UTCVendor advisory
- 2026-07-18 05:33 UTCGHSA enrichment
- 2026-07-18 01:47 UTCVendor advisory
- 2026-07-18 01:47 UTCGHSA enrichment
- 2026-07-17 22:01 UTCVendor advisory
- 2026-07-17 22:01 UTCGHSA enrichment
- 2026-07-17 18:15 UTCVendor advisory
- 2026-07-17 18:15 UTCGHSA enrichment
- 2026-07-17 14:29 UTCVendor advisory
- 2026-07-17 14:29 UTCGHSA enrichment
- 2026-07-17 10:43 UTCVendor advisory
- 2026-07-17 10:43 UTCGHSA enrichment
- 2026-07-17 06:58 UTCVendor advisory
- 2026-07-17 06:58 UTCGHSA enrichment
- 2026-07-17 03:12 UTCVendor advisory
- 2026-07-17 03:12 UTCGHSA enrichment
- 2026-07-16 23:26 UTCVendor advisory
- 2026-07-16 23:26 UTCGHSA enrichment
- 2026-07-16 19:41 UTCVendor advisory
- 2026-07-16 19:41 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 15:55 UTCVendor advisory
- 2026-07-16 15:54 UTCGHSA enrichment
- 2026-07-16 12:07 UTCGHSA enrichment
- 2026-07-16 08:22 UTCVendor advisory
- 2026-07-16 08:22 UTCGHSA enrichment
- 2026-07-16 04:36 UTCVendor advisory
- 2026-07-16 04:36 UTCGHSA enrichment
- 2026-07-16 00:51 UTCVendor advisory
- 2026-07-16 00:51 UTCGHSA enrichment
- 2026-07-15 21:05 UTCVendor advisory
- 2026-07-15 21:05 UTCGHSA enrichment
- 2026-07-15 17:19 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Nucleihttp/cves/2023/CVE-2023-41763.yamlFirst seen Jan 1, 2023
Skype for Business 2019 (SfB) - Blind Server-side Request Forgery
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-918
Frequently asked(6)
What is CVE-2023-41763?
When was CVE-2023-41763 disclosed?
Is CVE-2023-41763 actively exploited?
What is the CVSS score of CVE-2023-41763?
Which products are affected by CVE-2023-41763?
How do I remediate CVE-2023-41763?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-41763
Is Your Infrastructure Affected by CVE-2023-41763?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.