# CVE-2023-37476: Zip slip in OpenRefine

> Attackers can execute arbitrary code by tricking users into importing malicious OpenRefine project files containing path traversal payloads.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jul 2023
- **Updated:** 10 Jun 2025
- **Also known as:** DEBIAN-CVE-2023-37476, GHSA-m88m-crr9-jvqq, UBUNTU-CVE-2023-37476

## What is CVE-2023-37476?

CVE-2023-37476 is a medium-severity path traversal vulnerability in OpenRefine, published on 17 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OpenRefine is a free, open source tool for data processing. A carefully crafted malicious OpenRefine project tar file can be used to trigger arbitrary code execution in the context of the OpenRefine process if a user can be convinced to import it. The vulnerability exists in all versions of OpenRefine up to and including 3.7.3. Users should update to OpenRefine 3.7.4 as soon as possible. Users unable to upgrade should only import OpenRefine projects from trusted sources.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2023-37476?

2 open source packages ship an affected version, including org.openrefine:main. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.openrefine:main` | Maven | All versions | 3.7.4 |
| `org.openrefine:main` | Maven | All versions | 3.7.4 |

Products: Openrefine Openrefine.

## How do I fix CVE-2023-37476?

Upgrade org.openrefine:main to 3.7.4 or later.

## Is CVE-2023-37476 being exploited?

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

## Other vulnerabilities in OpenRefine

- [CVE-2023-41887](https://insights.sbomify.com/CVE-2023-41887/): Remote Code exec in project import with mysql jdbc url attack (critical 9.8)
- [CVE-2024-47878](https://insights.sbomify.com/CVE-2024-47878/): Reflected cross-site scripting vulnerability (XSS) in GData extension (authorized.vt) (high 8.1)
- [CVE-2024-47880](https://insights.sbomify.com/CVE-2024-47880/): OpenRefine has a reflected cross-site scripting vulnerability from POST request in ExportRowsCommand (high 8.1)
- [CVE-2024-47881](https://insights.sbomify.com/CVE-2024-47881/): OpenRefine's SQLite integration allows filesystem access, remote code execution (RCE) (high 8.1)
- [CVE-2024-47879](https://insights.sbomify.com/CVE-2024-47879/): OpenRefine's PreviewExpressionCommand, which is eval, lacks protection against cross-site request forgery (CSRF) (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37476 and fix it if it is affected.

What it is: CVE-2023-37476 is a medium-severity path traversal vulnerability in OpenRefine, published on 17 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-37476 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.openrefine:main (Maven): affected all versions; fixed in 3.7.4
- org.openrefine:main (Maven): affected all versions; fixed in 3.7.4

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-2023-37476/ (Markdown: https://insights.sbomify.com/CVE-2023-37476/index.md)
```

## Sources

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

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