CVE-2024-47882: medium-severity vulnerability in OpenRefine
OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.9epss 0.5%
OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the built-in "Something went wrong!" error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message. It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, which may be difficult. However, out-of-tree extensions may add their own calls to `respondWithErrorPage`. Version 3.8.3 has a fix for this issue.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N
Affected products
OpenRefine · OpenRefineRelated CVEs — OpenRefine
In the same product, most dangerous first.
CVE-2023-41887CRITICALRemote Code exec in project import with mysql jdbc url attackEPSS 42.5%CVE-2024-23833HIGHOpenRefine JDBC Attack VulnerabilityEPSS 1.0%CVE-2023-41886HIGHOpenRefine vulnerable to arbitrary file read in project import with mysql jdbc url attackEPSS 1.0%CVE-2024-47881HIGHOpenRefine's SQLite integration allows filesystem access, remote code execution (RCE)EPSS 0.7%CVE-2023-37476MEDIUMZip slip in OpenRefineEPSS 0.6%CVE-2024-49760HIGHOpenRefine has a path traversal in LoadLanguageCommandEPSS 0.6%