<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 31 May 2026 13:05:25 +0000</lastBuildDate>
    <item>
      <title>2b5558ea-ae41-4205-b625-8280b0a2c7b1</title>
      <link>https://vulnerability.circl.lu/sighting/2b5558ea-ae41-4205-b625-8280b0a2c7b1/export</link>
      <description>{"uuid": "2b5558ea-ae41-4205-b625-8280b0a2c7b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-47882", "type": "published-proof-of-concept", "source": "https://github.com/OpenRefine/OpenRefine/security/advisories/GHSA-j8hp-f2mj-586g", "content": "", "creation_timestamp": "2024-10-24T06:11:21.000000Z"}</description>
      <content:encoded>{"uuid": "2b5558ea-ae41-4205-b625-8280b0a2c7b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-47882", "type": "published-proof-of-concept", "source": "https://github.com/OpenRefine/OpenRefine/security/advisories/GHSA-j8hp-f2mj-586g", "content": "", "creation_timestamp": "2024-10-24T06:11:21.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/2b5558ea-ae41-4205-b625-8280b0a2c7b1/export</guid>
      <pubDate>Thu, 24 Oct 2024 06:11:21 +0000</pubDate>
    </item>
    <item>
      <title>2081b217-4017-49d2-81b4-89ddfce1d642</title>
      <link>https://vulnerability.circl.lu/sighting/2081b217-4017-49d2-81b4-89ddfce1d642/export</link>
      <description>{"uuid": "2081b217-4017-49d2-81b4-89ddfce1d642", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-47882", "type": "seen", "source": "https://t.me/cvedetector/8856", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47882 - OpenRefine HTML Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47882 \nPublished : Oct. 24, 2024, 9:15 p.m. | 36\u00a0minutes ago \nDescription : 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. \nSeverity: 5.9 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"24 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-25T00:21:33.000000Z"}</description>
      <content:encoded>{"uuid": "2081b217-4017-49d2-81b4-89ddfce1d642", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-47882", "type": "seen", "source": "https://t.me/cvedetector/8856", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47882 - OpenRefine HTML Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47882 \nPublished : Oct. 24, 2024, 9:15 p.m. | 36\u00a0minutes ago \nDescription : 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. \nSeverity: 5.9 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"24 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-25T00:21:33.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/2081b217-4017-49d2-81b4-89ddfce1d642/export</guid>
      <pubDate>Fri, 25 Oct 2024 00:21:33 +0000</pubDate>
    </item>
  </channel>
</rss>
