<?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://db.gcve.eu</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, 03 May 2026 09:01:02 +0000</lastBuildDate>
    <item>
      <title>56d86f21-7d49-40f9-a4ef-f46b4babd279</title>
      <link>https://db.gcve.eu/sighting/56d86f21-7d49-40f9-a4ef-f46b4babd279/export</link>
      <description>{"uuid": "56d86f21-7d49-40f9-a4ef-f46b4babd279", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5726", "type": "seen", "source": "https://t.me/cvedetector/1139", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-5726 - WordPress Timeline Event History PHP Object Injection\", \n  \"Content\": \"CVE ID : CVE-2024-5726 \nPublished : July 18, 2024, 2:15 a.m. | 43\u00a0minutes ago \nDescription : The Timeline Event History plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1 via deserialization of untrusted input 'timelines-data' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. \nSeverity: 8.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-18T05:05:47.000000Z"}</description>
      <content:encoded>{"uuid": "56d86f21-7d49-40f9-a4ef-f46b4babd279", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5726", "type": "seen", "source": "https://t.me/cvedetector/1139", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-5726 - WordPress Timeline Event History PHP Object Injection\", \n  \"Content\": \"CVE ID : CVE-2024-5726 \nPublished : July 18, 2024, 2:15 a.m. | 43\u00a0minutes ago \nDescription : The Timeline Event History plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1 via deserialization of untrusted input 'timelines-data' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. \nSeverity: 8.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-18T05:05:47.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/56d86f21-7d49-40f9-a4ef-f46b4babd279/export</guid>
      <pubDate>Thu, 18 Jul 2024 05:05:47 +0000</pubDate>
    </item>
    <item>
      <title>def8317f-5015-45fe-a781-8b7289796243</title>
      <link>https://db.gcve.eu/sighting/def8317f-5015-45fe-a781-8b7289796243/export</link>
      <description>{"uuid": "def8317f-5015-45fe-a781-8b7289796243", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57261", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3liipeisizy23", "content": "", "creation_timestamp": "2025-02-19T02:15:31.940209Z"}</description>
      <content:encoded>{"uuid": "def8317f-5015-45fe-a781-8b7289796243", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57261", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3liipeisizy23", "content": "", "creation_timestamp": "2025-02-19T02:15:31.940209Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/def8317f-5015-45fe-a781-8b7289796243/export</guid>
      <pubDate>Wed, 19 Feb 2025 02:15:31 +0000</pubDate>
    </item>
    <item>
      <title>b8f3a666-e1be-4aa2-9a07-8046b29a018e</title>
      <link>https://db.gcve.eu/sighting/b8f3a666-e1be-4aa2-9a07-8046b29a018e/export</link>
      <description>{"uuid": "b8f3a666-e1be-4aa2-9a07-8046b29a018e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57262", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3liipelzwma23", "content": "", "creation_timestamp": "2025-02-19T02:15:35.231916Z"}</description>
      <content:encoded>{"uuid": "b8f3a666-e1be-4aa2-9a07-8046b29a018e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57262", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3liipelzwma23", "content": "", "creation_timestamp": "2025-02-19T02:15:35.231916Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/b8f3a666-e1be-4aa2-9a07-8046b29a018e/export</guid>
      <pubDate>Wed, 19 Feb 2025 02:15:35 +0000</pubDate>
    </item>
    <item>
      <title>eb087bc0-54e1-43ad-9425-77b52e5f44d2</title>
      <link>https://db.gcve.eu/sighting/eb087bc0-54e1-43ad-9425-77b52e5f44d2/export</link>
      <description>{"uuid": "eb087bc0-54e1-43ad-9425-77b52e5f44d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57261", "type": "seen", "source": "https://t.me/cvedetector/18399", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57261 - Barebox Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57261 \nPublished : Feb. 19, 2025, 2:15 a.m. | 1\u00a0hour, 58\u00a0minutes ago \nDescription : In barebox before 2025.01.0, request2size in common/dlmalloc.c has an integer overflow, a related issue to CVE-2024-57258. \nSeverity: 7.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-19T05:21:58.000000Z"}</description>
      <content:encoded>{"uuid": "eb087bc0-54e1-43ad-9425-77b52e5f44d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57261", "type": "seen", "source": "https://t.me/cvedetector/18399", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57261 - Barebox Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57261 \nPublished : Feb. 19, 2025, 2:15 a.m. | 1\u00a0hour, 58\u00a0minutes ago \nDescription : In barebox before 2025.01.0, request2size in common/dlmalloc.c has an integer overflow, a related issue to CVE-2024-57258. \nSeverity: 7.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-19T05:21:58.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/eb087bc0-54e1-43ad-9425-77b52e5f44d2/export</guid>
      <pubDate>Wed, 19 Feb 2025 05:21:58 +0000</pubDate>
    </item>
    <item>
      <title>680da8ce-032a-4a05-a52e-8d525b92e6f6</title>
      <link>https://db.gcve.eu/sighting/680da8ce-032a-4a05-a52e-8d525b92e6f6/export</link>
      <description>{"uuid": "680da8ce-032a-4a05-a52e-8d525b92e6f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57262", "type": "seen", "source": "https://t.me/cvedetector/18400", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57262 - Barebox ext4fs Read Symlink Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57262 \nPublished : Feb. 19, 2025, 2:15 a.m. | 1\u00a0hour, 58\u00a0minutes ago \nDescription : In barebox before 2025.01.0, ext4fs_read_symlink has an integer overflow for zalloc (adding one to an le32 variable) via a crafted ext4 filesystem with an inode size of 0xffffffff, resulting in a malloc of zero and resultant memory overwrite, a related issue to CVE-2024-57256. \nSeverity: 7.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-19T05:21:59.000000Z"}</description>
      <content:encoded>{"uuid": "680da8ce-032a-4a05-a52e-8d525b92e6f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57262", "type": "seen", "source": "https://t.me/cvedetector/18400", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57262 - Barebox ext4fs Read Symlink Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57262 \nPublished : Feb. 19, 2025, 2:15 a.m. | 1\u00a0hour, 58\u00a0minutes ago \nDescription : In barebox before 2025.01.0, ext4fs_read_symlink has an integer overflow for zalloc (adding one to an le32 variable) via a crafted ext4 filesystem with an inode size of 0xffffffff, resulting in a malloc of zero and resultant memory overwrite, a related issue to CVE-2024-57256. \nSeverity: 7.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-19T05:21:59.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/680da8ce-032a-4a05-a52e-8d525b92e6f6/export</guid>
      <pubDate>Wed, 19 Feb 2025 05:21:59 +0000</pubDate>
    </item>
    <item>
      <title>abd5e5a8-6101-4bd7-8b94-348333f04b34</title>
      <link>https://db.gcve.eu/sighting/abd5e5a8-6101-4bd7-8b94-348333f04b34/export</link>
      <description>{"uuid": "abd5e5a8-6101-4bd7-8b94-348333f04b34", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57262", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lij3z5dsrk23", "content": "", "creation_timestamp": "2025-02-19T06:01:49.570019Z"}</description>
      <content:encoded>{"uuid": "abd5e5a8-6101-4bd7-8b94-348333f04b34", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57262", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lij3z5dsrk23", "content": "", "creation_timestamp": "2025-02-19T06:01:49.570019Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/abd5e5a8-6101-4bd7-8b94-348333f04b34/export</guid>
      <pubDate>Wed, 19 Feb 2025 06:01:49 +0000</pubDate>
    </item>
    <item>
      <title>725025fc-b107-40a1-aff6-01a0d191908c</title>
      <link>https://db.gcve.eu/sighting/725025fc-b107-40a1-aff6-01a0d191908c/export</link>
      <description>{"uuid": "725025fc-b107-40a1-aff6-01a0d191908c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57261", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lij3z5pkhq2c", "content": "", "creation_timestamp": "2025-02-19T06:01:50.243809Z"}</description>
      <content:encoded>{"uuid": "725025fc-b107-40a1-aff6-01a0d191908c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57261", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lij3z5pkhq2c", "content": "", "creation_timestamp": "2025-02-19T06:01:50.243809Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/725025fc-b107-40a1-aff6-01a0d191908c/export</guid>
      <pubDate>Wed, 19 Feb 2025 06:01:50 +0000</pubDate>
    </item>
  </channel>
</rss>
