<?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>Mon, 11 May 2026 06:41:12 +0000</lastBuildDate>
    <item>
      <title>59256ae8-feff-4819-81c6-443e8e75de9e</title>
      <link>https://vulnerability.circl.lu/sighting/59256ae8-feff-4819-81c6-443e8e75de9e/export</link>
      <description>{"uuid": "59256ae8-feff-4819-81c6-443e8e75de9e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-20232", "type": "seen", "source": "https://t.me/cvedetector/21233", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-20232 - Splunk Enterprise/Bypass Splunk Search Command Permissions\", \n  \"Content\": \"CVE ID : CVE-2025-20232 \nPublished : March 26, 2025, 10:15 p.m. | 33\u00a0minutes ago \nDescription : In Splunk Enterprise versions below 9.3.3, 9.2.5, and 9.1.8 and Splunk Cloud Platform versions below 9.3.2408.103, 9.2.2406.108, 9.2.2403.113, 9.1.2312.208 and 9.1.2308.212, a low-privileged user that does not hold the \u201cadmin\u201c or \u201cpower\u201c Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands on the \u201c/app/search/search\u201c endpoint through its \u201cs\u201c parameter. \nThe vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will. \nSeverity: 5.7 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-26T23:55:52.000000Z"}</description>
      <content:encoded>{"uuid": "59256ae8-feff-4819-81c6-443e8e75de9e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-20232", "type": "seen", "source": "https://t.me/cvedetector/21233", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-20232 - Splunk Enterprise/Bypass Splunk Search Command Permissions\", \n  \"Content\": \"CVE ID : CVE-2025-20232 \nPublished : March 26, 2025, 10:15 p.m. | 33\u00a0minutes ago \nDescription : In Splunk Enterprise versions below 9.3.3, 9.2.5, and 9.1.8 and Splunk Cloud Platform versions below 9.3.2408.103, 9.2.2406.108, 9.2.2403.113, 9.1.2312.208 and 9.1.2308.212, a low-privileged user that does not hold the \u201cadmin\u201c or \u201cpower\u201c Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands on the \u201c/app/search/search\u201c endpoint through its \u201cs\u201c parameter. \nThe vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will. \nSeverity: 5.7 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-26T23:55:52.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/59256ae8-feff-4819-81c6-443e8e75de9e/export</guid>
      <pubDate>Wed, 26 Mar 2025 23:55:52 +0000</pubDate>
    </item>
  </channel>
</rss>
