<?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, 10 May 2026 03:01:22 +0000</lastBuildDate>
    <item>
      <title>9d6a918f-3499-4ecd-93aa-7537080f8007</title>
      <link>https://vulnerability.circl.lu/sighting/9d6a918f-3499-4ecd-93aa-7537080f8007/export</link>
      <description>{"uuid": "9d6a918f-3499-4ecd-93aa-7537080f8007", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-8548", "type": "seen", "source": "https://t.me/cvedetector/6721", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-8548 - \"KB Support WordPress Help Desk and Knowledge Base Unauthorized Access Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-8548 \nPublished : Oct. 1, 2024, 8:15 a.m. | 43\u00a0minutes ago \nDescription : The KB Support \u2013 WordPress Help Desk and Knowledge Base plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on several functions in all versions up to, and including, 1.6.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform multiple administrative actions, such as replying to arbitrary tickets, updating the status of any post, deleting any post, adding notes to tickets, flagging or unflagging tickets, and adding or removing ticket participants. \nSeverity: 8.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-01T11:04:06.000000Z"}</description>
      <content:encoded>{"uuid": "9d6a918f-3499-4ecd-93aa-7537080f8007", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-8548", "type": "seen", "source": "https://t.me/cvedetector/6721", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-8548 - \"KB Support WordPress Help Desk and Knowledge Base Unauthorized Access Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-8548 \nPublished : Oct. 1, 2024, 8:15 a.m. | 43\u00a0minutes ago \nDescription : The KB Support \u2013 WordPress Help Desk and Knowledge Base plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on several functions in all versions up to, and including, 1.6.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform multiple administrative actions, such as replying to arbitrary tickets, updating the status of any post, deleting any post, adding notes to tickets, flagging or unflagging tickets, and adding or removing ticket participants. \nSeverity: 8.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-01T11:04:06.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/9d6a918f-3499-4ecd-93aa-7537080f8007/export</guid>
      <pubDate>Tue, 01 Oct 2024 11:04:06 +0000</pubDate>
    </item>
    <item>
      <title>0596af5d-2fb2-4ed9-8e00-090f8841541b</title>
      <link>https://vulnerability.circl.lu/sighting/0596af5d-2fb2-4ed9-8e00-090f8841541b/export</link>
      <description>{"uuid": "0596af5d-2fb2-4ed9-8e00-090f8841541b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-8548", "type": "seen", "source": "Telegram/Tr1OAhYrBYhi37hteV9sRLNErIQj_-Fa1RxMst-A3IeKG0O5", "content": "", "creation_timestamp": "2025-02-14T09:47:01.000000Z"}</description>
      <content:encoded>{"uuid": "0596af5d-2fb2-4ed9-8e00-090f8841541b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-8548", "type": "seen", "source": "Telegram/Tr1OAhYrBYhi37hteV9sRLNErIQj_-Fa1RxMst-A3IeKG0O5", "content": "", "creation_timestamp": "2025-02-14T09:47:01.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/0596af5d-2fb2-4ed9-8e00-090f8841541b/export</guid>
      <pubDate>Fri, 14 Feb 2025 09:47:01 +0000</pubDate>
    </item>
    <item>
      <title>07847ab5-18fd-47fa-9233-2969ceccfdac</title>
      <link>https://vulnerability.circl.lu/sighting/07847ab5-18fd-47fa-9233-2969ceccfdac/export</link>
      <description>{"uuid": "07847ab5-18fd-47fa-9233-2969ceccfdac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-8548", "type": "seen", "source": "https://bsky.app/profile/cyberhub.blog/post/3miz4k72bbl2q", "content": "", "creation_timestamp": "2026-04-08T20:20:15.369700Z"}</description>
      <content:encoded>{"uuid": "07847ab5-18fd-47fa-9233-2969ceccfdac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-8548", "type": "seen", "source": "https://bsky.app/profile/cyberhub.blog/post/3miz4k72bbl2q", "content": "", "creation_timestamp": "2026-04-08T20:20:15.369700Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/07847ab5-18fd-47fa-9233-2969ceccfdac/export</guid>
      <pubDate>Wed, 08 Apr 2026 20:20:15 +0000</pubDate>
    </item>
  </channel>
</rss>
