Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-49760 Overview
CVE-2024-49760 is a path traversal vulnerability [CWE-22] in OpenRefine, an open source tool for working with messy data. The load-language command accepts a lang parameter and constructs the localization file path as translations-$LANG.json. In versions prior to 3.8.3, the command does not validate that the resulting path remains within the expected langs directory. An attacker can supply a crafted lang value to read other JSON files from the file system. OpenRefine 3.8.3 addresses the issue by normalizing the resolved path and verifying it against the langs directory.
Critical Impact
Unauthenticated network-accessible attackers can read arbitrary JSON files on the host where OpenRefine is running, exposing configuration and application data.
Affected Products
- OpenRefine versions prior to 3.8.3
- Deployments exposing the OpenRefine web interface over the network
- Any environment where OpenRefine processes untrusted lang input
Discovery Timeline
- 2024-10-24 - CVE-2024-49760 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-49760
Vulnerability Analysis
The flaw resides in LoadLanguageCommand.java within the OpenRefine servlet. The handler reads a lang request parameter and concatenates it into a file path string of the form translation-$LANG.json. The constructed File object is then opened with a FileInputStream without canonicalizing the resolved path. An attacker can supply traversal sequences such as ../ inside the lang value to break out of the langs directory. Because the server returns the file contents to the HTTP client, this results in disclosure of JSON files elsewhere on the host.
Root Cause
The root cause is missing path validation after file resolution. The original code built new File(module.getPath(), "langs" + File.separator + strLangFile) and trusted the result without checking that the normalized absolute path remained a child of the langs directory. This is a classic directory slip pattern tracked under CWE-22.
Attack Vector
Exploitation requires only network access to the OpenRefine HTTP interface and no authentication. The attacker issues a request to the load-language endpoint and supplies a lang parameter containing traversal segments that cause the resolved path to point at a JSON file outside langs. Information disclosure is limited to files with a .json suffix and readable by the OpenRefine process.
ButterflyModule module = servlet.getModule(strModule);
String strLangFile = "translation-" + strLang + ".json";
String strMessage = "[" + strModule + ":" + strLangFile + "]";
- File langFile = new File(module.getPath(), "langs" + File.separator + strLangFile);
+ File langsDir = new File(module.getPath(), "langs");
+ File langFile = new File(langsDir, strLangFile);
+ if (!langFile.toPath().normalize().toAbsolutePath().startsWith(langsDir.toPath().normalize().toAbsolutePath())) {
+ logger.error("Security: Attempt to escape the langs directory to read another file");
+ return null;
+ }
FileInputStream fisLang = null;
try {
Source: OpenRefine commit 24d0840. The patch resolves and normalizes the candidate file path, then verifies it starts with the normalized langs directory before opening it.
Detection Methods for CVE-2024-49760
Indicators of Compromise
- HTTP requests to the load-language command containing ../, ..\\, URL-encoded %2e%2e%2f, or absolute path fragments in the lang parameter.
- OpenRefine server log entries referencing translation- filenames that do not match known locale codes.
- Error log lines containing Security: Attempt to escape the langs directory to read another file after upgrading to 3.8.3.
Detection Strategies
- Inspect reverse proxy and application access logs for load-language requests with suspicious lang values and alert on traversal patterns.
- Monitor the OpenRefine process for reads of JSON files outside the installation langs/ subdirectory.
- Correlate anomalous load-language request volume from a single source address with subsequent file access events on the host.
Monitoring Recommendations
- Forward OpenRefine web and application logs to a centralized logging platform and apply detections for CWE-22 patterns in query parameters.
- Baseline normal lang parameter values against the set of locales shipped with the deployed OpenRefine version.
- Enable file integrity and access monitoring on sensitive directories reachable by the OpenRefine service account.
How to Mitigate CVE-2024-49760
Immediate Actions Required
- Upgrade OpenRefine to version 3.8.3 or later, which contains the path validation fix.
- Restrict network exposure of the OpenRefine interface to trusted hosts and authenticated users only.
- Review access logs for prior exploitation attempts against the load-language endpoint.
Patch Information
The fix is committed in OpenRefine commit 24d0840 and tracked in GitHub Security Advisory GHSA-qfwq-6jh6-8xx4. Upgrading to OpenRefine 3.8.3 normalizes the resolved language file path and rejects any path that escapes the langs directory.
Workarounds
- Place OpenRefine behind a reverse proxy that rejects requests to /command/core/load-language containing .., /, \\, or encoded traversal sequences in the lang parameter.
- Run OpenRefine under a dedicated low-privilege account whose read permissions are limited to the application directory.
- Bind OpenRefine to localhost and require VPN or SSH tunneling for remote access until the patch is applied.
# Example reverse proxy filter (NGINX) to block traversal in the lang parameter
location /command/core/load-language {
if ($arg_lang ~* "(\.\.|/|\\|%2e%2e|%2f|%5c)") {
return 400;
}
proxy_pass http://openrefine_upstream;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

