CVE-2025-4700
8.7GitLab · GitLab CE/EE
A cross-site scripting (XSS) vulnerability in GitLab CE/EE allows authenticated attackers to trigger unintended content rendering via specifically crafted inputs.
Executive summary
A high-severity cross-site scripting vulnerability in GitLab CE/EE allows authenticated attackers to execute malicious scripts, posing a significant risk to user session integrity and application security.
Vulnerability
The vulnerability is a cross-site scripting (XSS) flaw (CWE-79) triggered by improper input neutralization. An authenticated attacker with low privileges can exploit this by submitting crafted content that is rendered by the application, leading to malicious script execution in the context of other users.
Business impact
The exploitation of this vulnerability can lead to unauthorized actions performed on behalf of legitimate users, including session hijacking or the theft of sensitive data. With a CVSS score of 8.7, the impact is considered high due to the potential for total compromise of user-level confidentiality and integrity within the GitLab environment. Such breaches can lead to significant reputational damage and the exposure of proprietary source code or infrastructure configurations.
Remediation
Immediate Action: Upgrade GitLab CE/EE installations to version 18.0.5, 18.1.3, 18.2.1, or higher immediately to apply the vendor-provided security patches.
Proactive Monitoring: Review application access logs for suspicious input patterns or unusual activity associated with user-generated content rendering.
Compensating Controls: Utilize a Web Application Firewall (WAF) with updated rulesets to filter potentially malicious scripts and prevent the injection of harmful payloads.
Exploitation status
Public Exploit Available: Yes — a published proof-of-concept exists as documented in the HackerOne report linked in the CVE references.
Analyst recommendation
Given the high CVSS score and the public availability of technical details regarding the exploit, this vulnerability presents a clear and present risk. Organizations should prioritize the deployment of the vendor-supplied patches to all affected instances. Failure to remediate this issue could allow attackers to bypass standard security controls, necessitating an immediate patching cycle to ensure the integrity of the development environment.
More GitLab CVEs
Sources
Originally found and disclosed by Thanks [joaxcar](https://hackerone.com/joaxcar) for reporting this vulnerability through our HackerOne bug bounty progra, per the CVE Program record.
- GitLab Issue #542915 Issue tracker
- HackerOne Bug Bounty Report #3120062 Exploit / PoC