CVE-2022-23737 json
Improper Privilege Management in GitHub Enterprise Server leading to page creation and deletion
published 2022-12-01 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-28673
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
An improper privilege management vulnerability was identified in GitHub Enterprise Server that allowed users with improper privileges to create or delete pages via the API. To exploit this vulnerability, an attacker would need to be added to an organization's repo with write permissions. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.7 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, and 3.6.3. This vulnerability was reported via the GitHub Bug Bounty program.
Patch / fix
- GitHub GitHub Enterprise Server 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- GitHub GitHub Enterprise Server
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
- docs.github.com /en/enterprise-server%403.2/admin/release-notes#3.2.20
- docs.github.com /en/enterprise-server%403.3/admin/release-notes#3.3.15
- docs.github.com /en/enterprise-server%403.4/admin/release-notes#3.4.10
- docs.github.com /en/enterprise-server%403.5/admin/release-notes#3.5.7
- docs.github.com /en/enterprise-server%403.6/admin/release-notes#3.6.3
Sources
- CVE List CVE-2022-23737
- NVD CVE-2022-23737
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.