CVE-2024-47880

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2024-10-24. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2024-2977 (ENISA EUVD) · GHSA-79jv-5226-783f (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the export-rows command can be used in such a way that it reflects part of the request verbatim, with a Content-Type header also taken from the request. An attacker could lead a user to a malicious page that submits a form POST that contains embedded JavaScript code. This code would then be included in the response, along with an attacker-controlled Content-Type header, and so potentially executed in the victim's browser as if it was part of OpenRefine. The attacker-provided code can do anything the user can do, including deleting projects, retrieving database passwords, or executing arbitrary Jython or Closure expressions, if those extensions are also present. The attacker must know a valid project ID of a project that contains at least one row. Version 3.8.3 fixes the issue.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 24, 2024

Last Modified

October 30, 2024

Advisory Details (2)

Auto-updated Sep 13, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Reflected cross-site scripting vulnerability (XSS) from POST request in ExportRowsCommand · Advisory · OpenRefine/OpenRefine · GitHub

https://github.com/OpenRefine/OpenRefine/security/advisories/GHSA-79jv-5226-783f
GitHub commit

commit 8060477fa538 (OpenRefine/OpenRefine)

Fix landed in OpenRefine/OpenRefine commit 8060477fa538 — awaiting tagged release

https://github.com/OpenRefine/OpenRefine/commit/8060477fa53842ebabf43b63e039745932fa629d

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenrefine (3.7.8-1ubuntu0.1) @ oracular2026-10-27ubuntu
mavenorg.openrefine:openrefine @ 3.8.3 (fixes < 3.8.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openrefine3.6.2-2, 3.6.2-2+deb12u1, 3.6.2-2+deb12u2
  • every version up to 3.6.2-2+deb12u3: fixed in 3.6.2-2+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openrefine—
  • every version up to 3.8.7-1: fixed in 3.8.7-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.openrefine:openrefine3.6-beta1 ... 3.8.2 (15 versions)
  • every version up to 3.8.3: fixed in 3.8.3
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 214 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-79jv-5226-783f · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-11-01 08:11 UTCEG score recompute
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-27 20:28 UTCEG score recompute
  9. 2026-10-27 20:28 UTCVendor advisory
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-25 17:00 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-20 10:24 UTCEG score recompute
  20. 2026-10-20 10:24 UTCVendor advisory
  21. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-18 06:57 UTCEG score recompute
  24. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 69 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-12 17:43 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-11 21:08 UTCEG score recompute
  7. 2026-10-11 16:01 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-10 10:33 UTCOSV refresh
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  19. 2026-09-30 19:55 UTCEG score recompute
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  21. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  23. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  24. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  25. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  26. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  29. 2026-09-20 20:03 UTCOSV refresh
  30. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  35. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  36. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  37. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  38. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  39. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  40. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  41. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  42. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  43. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  44. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  45. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  46. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  47. 2026-09-01 19:43 UTCOSV refresh
  48. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  49. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  50. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  51. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  52. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  53. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  54. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  55. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  56. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  57. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  58. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  59. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  60. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  61. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  62. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  63. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  64. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  65. 2026-08-15 21:37 UTCOSV refresh
  66. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  67. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  68. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  69. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.4% · 28th percentile

Frequently asked(5)

What is CVE-2024-47880?
CVE-2024-47880 is a high-severity vulnerability; its CVE record was published on October 24, 2024. OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the export-rows command can be used in such a way that it reflects part of the request verbatim, with a Content-Type header also taken from the request. An attacker could lead a user to a malicious page that…
When was the CVE record for CVE-2024-47880 published?
The CVE record for CVE-2024-47880 was published on October 24, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2024; the record at its source may have been updated since.
Is CVE-2024-47880 actively exploited?
CVE-2024-47880 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-47880?
CVE-2024-47880 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2024-47880?
A fix for CVE-2024-47880 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-47880

Explore →

Is Your Infrastructure Affected by CVE-2024-47880?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.