CVE-2023-7028: Weak Password Recovery Mechanism for Forgotten Password in GitLab
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which user account password reset emails could be delivered to an unverified email address.
Security readout for executives and security teams
Plain-English summary
CVE-2023-7028 is a critical GitLab account-takeover flaw. In affected GitLab CE/EE versions, password reset emails could be sent to an unverified email address. That can let an attacker reset a user’s password and access repositories, issues, CI/CD data, or administrative functions depending on the compromised account.
Executive priority
Treat as an immediate remediation item. The vulnerability affects account recovery, has a maximum CVSS score, and is in CISA KEV. Compromise could expose source code, secrets in repositories, CI/CD pipelines, and project governance data depending on account privileges.
Technical view
GitLab CE/EE versions 16.1 through 16.7 are affected below specific patch releases. The flaw is CWE-640 in the password recovery flow. CVSS is 10.0: network-accessible, low complexity, no privileges, no user interaction, scope changed, high confidentiality and integrity impact, with no availability impact stated.
Likely exposure
Organizations running self-managed GitLab CE/EE 16.1 before 16.1.6, 16.2 before 16.2.9, 16.3 before 16.3.7, 16.4 before 16.4.5, 16.5 before 16.5.6, 16.6 before 16.6.4, or 16.7 before 16.7.2 are exposed.
Exploitation context
CISA lists CVE-2023-7028 in the Known Exploited Vulnerabilities catalog, so active exploitation is supported by a government source. Public issue and bug bounty references exist. Do not treat this as theoretical; prioritize exposed internet-facing GitLab instances and high-privilege accounts.
Researcher notes
The public record identifies the vulnerable mechanism and affected version ranges, but this bundle does not provide complete IoCs or a vendor mitigation alternative beyond fixed versions. Use GitLab’s issue and HackerOne report for technical context, and avoid operationalizing exploit details.
Mitigation direction
Upgrade GitLab to 16.1.6, 16.2.9, 16.3.7, 16.4.5, 16.5.6, 16.6.4, or 16.7.2 or later.
Prioritize internet-facing GitLab instances and systems used for source code or CI/CD administration.
If immediate upgrade is blocked, check current GitLab vendor guidance for supported temporary controls.
Review password reset activity and account changes for suspicious behavior during the exposure window.
Validation and detection
Inventory all GitLab CE/EE instances and record exact versions.
Compare versions against the affected ranges and fixed release thresholds.
Confirm patched instances are at or above the relevant fixed version.
Check CISA KEV status for operational prioritization and remediation tracking.
Review referenced GitLab and HackerOne materials for technical confirmation without reproducing exploit steps.
The source record changed after analysis. Treat this automated context as pending refresh.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-640: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-640 · source CWE mapping
Weak Password Recovery Mechanism for Forgotten Password
Weak Password Recovery Mechanism for Forgotten Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.