GitLab Community Edition/Enterprise Edition up to 16.11.4/17.0.2/17.1.0 GraphQL API cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 16.11.4/17.0.2/17.1.0 and classified as problematic. This issue affects some unknown processing of the component GraphQL API. The manipulation results in cross-site request forgery. This vulnerability was named CVE-2024-4994. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 16.11.4/17.0.2/17.1.0. It has been classified as problematic. Affected is an unknown code of the component GraphQL API. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1.0 before 16.11.5, all versions starting from 17.0 before 17.0.3, all versions starting from 17.1.0 before 17.1.1 which allowed for a CSRF attack on GitLab's GraphQL API leading to the execution of arbitrary GraphQL mutations.
The weakness was presented by ahacker1. The advisory is shared for download at gitlab.com. This vulnerability is traded as CVE-2024-4994 since 05/16/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.
Upgrading to version 16.11.5, 17.0.3 or 17.1.1 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 16.11.5/17.0.3/17.1.1
Timeline
05/16/2024 CVE reserved06/20/2025 Advisory disclosed
06/20/2025 VulDB entry created
08/12/2025 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Researcher: ahacker1
Status: Confirmed
CVE: CVE-2024-4994 (🔒)
GCVE (CVE): GCVE-0-2024-4994
GCVE (VulDB): GCVE-100-313548
Entry
Created: 06/20/2025 21:20Updated: 08/12/2025 17:15
Changes: 06/20/2025 21:20 (66), 08/12/2025 17:15 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.