CVE-2023-51380 | Incorrect Authorization allows Read Access to Issue Comments in GitHub Enterprise Server

An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed issue comments to be read with an improperly scoped token. This vulnerability affected all versions of GitHub Enterprise Server since 3.7 and was fixed in version 3.7.19, 3.8.12, 3.9.7, 3.10.4, and 3.11.1.

Published: 2023-12-21 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2023-51380 is rated Low Risk (23.9/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.47%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-51380

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.17% 0.47% +0.30%
2 2026-03-04 0.14% 0.17% +0.03%
3 2026-03-01 0.14%

Full EPSS history (26 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-51380

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.7 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.2 1.4 [email protected]
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]

Weakness enumeration for CVE-2023-51380

Affected software / configurations for CVE-2023-51380

Vendor Product Version Raw CPE
github enterprise_server >= 3.7.0, < 3.7.19 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*
github enterprise_server >= 3.8.0, < 3.8.12 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*
github enterprise_server >= 3.9.0, < 3.9.7 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*
github enterprise_server >= 3.10.0, < 3.10.4 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*
github enterprise_server 3.11.0 cpe:2.3:a:github:enterprise_server:3.11.0:*:*:*:*:*:*:*

References for CVE-2023-51380

cvelogic Threat Intelligence