What’s Vulnerable › Vulnerabilities

CVE-2024-47882: OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project

• Severity: medium (CVSS 6.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2024-10-24 · updated 2026-06-17
• Weakness: CWE-79

Description

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.

Affected products

• OpenRefine: before 3.8.3 — fixed in 3.8.3

How to fix

Upgrade to a fixed version: OpenRefine 3.8.3. Check the vendor advisory for mitigations.

References

• https://github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/error.vt#L52-L53
• https://github.com/OpenRefine/OpenRefine/commit/85594e75e7b36025f7b6a67dcd3ec253c5dff8c2
• https://github.com/OpenRefine/OpenRefine/security/advisories/GHSA-j8hp-f2mj-586g

Get alerted when CVE-2024-47882 or the next vulnerability affects your stack