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
GitLab instances in listed 16.x releases can send password reset emails to an unverified email address, creating a direct account-takeover risk. Because CISA lists this CVE in KEV, treat exposed affected GitLab servers as urgent until patched and reviewed.
Executive priority
Emergency priority. This is a critical account-takeover vulnerability with KEV-listed exploitation. Patch affected GitLab instances immediately, then verify whether sensitive repositories, CI/CD secrets, or administrator accounts could have been accessed.
Technical view
CVE-2023-7028 is a CWE-640 password recovery flaw in GitLab CE/EE. A network attacker needs no privileges, interaction, or local access. Affected versions are 16.1 before 16.1.6 through 16.7 before 16.7.2. CVSS 10.0 reflects high confidentiality and integrity impact.
Likely exposure
Organizations running self-managed GitLab CE/EE versions 16.1 through 16.7 are the primary exposure group. The bundle does not identify GitLab.com customer exposure or non-GitLab products as affected.
Exploitation context
Active exploitation is supported by the CISA Known Exploited Vulnerabilities listing. The public bundle also references a HackerOne report and a third-party analysis, but this assessment avoids exploit mechanics and does not infer exploitation beyond the KEV evidence.
Researcher notes
The key evidence is the CVE record, affected-version ranges, CVSS vector, CWE-640 classification, and KEV status. The bundle does not provide full incident indicators, complete exploit telemetry, or comprehensive post-compromise guidance.
Mitigation direction
Upgrade GitLab 16.1 to 16.1.6 or later.
Upgrade GitLab 16.2 to 16.2.9 or later.
Upgrade GitLab 16.3 to 16.3.7 or later.
Upgrade GitLab 16.4 to 16.4.5 or later.
Upgrade GitLab 16.5 to 16.5.6, 16.6.4, or 16.7.2 as applicable.
Check current GitLab vendor guidance for any additional hardening or investigation steps.
Validation and detection
Inventory all self-managed GitLab CE/EE instances and record exact versions.
Confirm no instance runs affected versions before the listed fixed releases.
Review account password reset activity for unexpected recipients or timing.
Prioritize internet-facing GitLab systems and privileged user accounts.
Verify remediation through package version, application UI, or approved asset records.
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.