CVE-2023-7028: GitLab Community and Enterprise Editions Improper Access Control Vulnerability
Affects GitLab GitLab CE/EESource CISA KEV
Exploited in the wild · KEV due 22 May 2024 · public exploit available (Metasploit, Exploit-DB) · 94% EPSS : apply the vendor's fix or mitigations to GitLab CE/EE now.
Data as of 10/24/2026, 22:15:59 UTC
- Exploitation
Actively exploited – in CISA KEV since 05/01/2024
- KEV deadline
- 05/22/2024 US federal agencies must patch by this date; a sensible deadline for everyone else.
- EPSS
- 94.4% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Public exploits
- 1 Metasploit module, 1 Exploit-DB entry, a Nuclei detection templatePublic attack or detection tooling exists; see Public exploits below.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NWhat to do
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploits and detection
Nuclei detection templates
Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.
Description
GitLab Community and Enterprise Editions contain an improper access control vulnerability. This allows an attacker to trigger password reset emails to be sent to an unverified email address to ultimately facilitate an account takeover.
Weaknesses
- CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.