Threats / GitLab / CVE-2023-7028
CVE-2023-7028
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
GitLab CE/EE vulnerability
GitLab CE/EE contains an improper access control flaw allowing attackers to trigger password reset emails to unverified addresses, enabling account takeover.
Verdict
Today item — known-exploited.
An attacker exploits weak email verification controls to reset credentials on accounts they do not own, gaining unauthorized access to GitLab instances and hosted repositories. Active exploitation in the wild increases risk.
CISA KEV Yes · 2024-05-015EPSS 0.94647 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-05-01).
Probability (EPSS)
EPSS 0.94647 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) · Affected: GitLab, GitLab CE/EE. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-640 CWE-640 — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 110 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a target GitLab account and trigger a password reset to an unverified email address I control.
Business
Unauthorized access to source code repositories, CI/CD pipelines, and sensitive project data compromises software supply chain integrity.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I receive the password reset link and establish persistent access to the compromised account.
Business
Attackers can modify code, inject malicious commits, or exfiltrate intellectual property, leading to data breach and operational disruption.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate privileges or pivot to other systems accessible through the GitLab instance.
Business
Lateral movement through integrated development environments and deployment systems increases blast radius and recovery costs.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05