Security readout for executives and security teams
Plain-English summary
OpenRefine can be compromised if a user imports a malicious project archive. The issue allows files from that archive to escape their intended location and run code as the OpenRefine process. Business risk depends on whether staff exchange or import OpenRefine projects. Upgrade to 3.7.4 and treat untrusted project files as unsafe.
Executive priority
Prioritize remediation where OpenRefine is used with third-party datasets or project sharing. This is not a wormable internet-facing issue, but it can turn a trusted data tool into a code-execution path if users import hostile project files.
Technical view
CVE-2023-37476 is a Zip Slip/path traversal flaw (CWE-22) in OpenRefine project tar import affecting versions before 3.7.4. A crafted project archive can write outside the expected extraction path and lead to arbitrary code execution in the OpenRefine process context. CVSS 3.1 is 5.5, with required user interaction and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to environments running OpenRefine before 3.7.4, especially desktops or shared data-processing systems where users import project tar files from email, shared drives, or external collaborators.
Exploitation context
Sources describe exploitation through a malicious OpenRefine project tar file imported by a user. The source bundle does not cite CISA KEV listing or active exploitation evidence, so active exploitation should not be assumed.
Researcher notes
The public record identifies path traversal during OpenRefine project tar handling and a fix in 3.7.4. Keep validation focused on version exposure and project-import trust boundaries. Do not infer broader OpenRefine products or active exploitation from the provided sources.
Mitigation direction
- Upgrade OpenRefine to version 3.7.4 or later.
- If upgrade is delayed, import only OpenRefine projects from trusted sources.
- Warn users not to open unexpected OpenRefine project archives.
- Check vendor advisory and release notes for any environment-specific guidance.
Validation and detection
- Inventory OpenRefine installations and confirm versions are 3.7.4 or later.
- Review workflows for project imports from external or untrusted parties.
- Check endpoint logs for suspicious activity around OpenRefine project imports.
- Confirm users handling OpenRefine projects received file-origin guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-37476 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L2.13.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/OpenRefine/OpenRefine/security/advisories/GHSA-m88m-crr9-jvqqCVE reference · x_refsource_CONFIRM
- https://github.com/OpenRefine/OpenRefine/commit/e9c1e65d58b47aec8cd676bd5c07d97b002f205eCVE reference · x_refsource_MISC
- https://github.com/OpenRefine/OpenRefine/releases/tag/3.7.4CVE reference · x_refsource_MISC
- https://www.sonarsource.com/blog/openrefine-zip-slipCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.