# CVE-2024-37306: CVAT's export and backup-related API endpoints are susceptible to CSRF

> Attackers can trick logged-in users into exporting data to attacker-controlled cloud storage, allowing file overwrites and data theft.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jpf9-646h-4px7

## What is CVE-2024-37306?

CVE-2024-37306 is a high-severity vulnerability in cvat-ai cvat, published on 13 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Computer Vision Annotation Tool (CVAT) is an interactive video and image annotation tool for computer vision. Starting in version 2.2.0 and prior to version 2.14.3, if an attacker can trick a logged-in CVAT user into visiting a malicious URL, they can initiate a dataset export or a backup from a project, task or job that the victim user has permission to export into a cloud storage that the victim user has access to. The name of the resulting file can be chosen by the attacker. This implies that the attacker can overwrite arbitrary files in any cloud storage that the victim can access and, if the attacker has read access to the cloud storage used in the attack, they can obtain media files, annotations, settings and other information from any projects, tasks or jobs that the victim has permission to export. Version 2.14.3 contains a fix for the issue. No known workarounds are available.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-37306?

It affects 1 product.


Products: Cvat Computer Vision Annotation Tool.

## How do I fix CVE-2024-37306?

No fix has been published for CVE-2024-37306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-37306 being exploited?

There is no known exploitation of CVE-2024-37306 in the wild and no public exploit code.

## Other vulnerabilities in cvat-ai cvat

- [CVE-2025-23045](https://insights.sbomify.com/CVE-2025-23045/): CVAT allows remote code execution via tracker Nuclio functions (high 8.7)
- [CVE-2026-23516](https://insights.sbomify.com/CVE-2026-23516/): CVAT vulnerable to XSS via skeleton SVG images (high 8.6)
- [CVE-2022-31188](https://insights.sbomify.com/CVE-2022-31188/): Server-Side Request Forgery Vulnerability in Computer Vision Annotation Tool (CVAT) (high 8.6)
- [CVE-2026-23526](https://insights.sbomify.com/CVE-2026-23526/): CVAT vulnerable to privilege escalation of users with staff status (high 8.5)
- [CVE-2024-37164](https://insights.sbomify.com/CVE-2024-37164/): CVAT SSRF via custom cloud storage endpoints (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37306 and fix it if it is affected.

What it is: CVE-2024-37306 is a high-severity vulnerability in cvat-ai cvat, published on 13 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-37306 in the wild and no public exploit code.

Affected product: cvat-ai cvat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-37306/ (Markdown: https://insights.sbomify.com/CVE-2024-37306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37306
- OSV: https://osv.dev/vulnerability/CVE-2024-37306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-37306/
Summaries are generated and may contain mistakes; the official description above is the record.