<?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>Mon, 01 Jun 2026 06:24:44 +0000</lastBuildDate>
    <item>
      <title>fa2b1dcd-7df5-4081-9620-889db3258efa</title>
      <link>https://db.gcve.eu/sighting/fa2b1dcd-7df5-4081-9620-889db3258efa/export</link>
      <description>{"uuid": "fa2b1dcd-7df5-4081-9620-889db3258efa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-0657", "type": "seen", "source": "https://t.me/cibsecurity/41398", "content": "\u203c CVE-2022-0657 \u203c\n\nThe 5 Stars Rating Funnel WordPress Plugin | RRatingg WordPress plugin before 1.2.54 does not properly sanitise, validate and escape lead ids before using them in a SQL statement via the rrtngg_delete_leads AJAX action, available to unauthenticated users, leading to an unauthenticated SQL injection issue. There is an attempt to sanitise the input, using sanitize_text_field(), however such function is not intended to prevent SQL injections.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-04-25T20:36:26.000000Z"}</description>
      <content:encoded>{"uuid": "fa2b1dcd-7df5-4081-9620-889db3258efa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-0657", "type": "seen", "source": "https://t.me/cibsecurity/41398", "content": "\u203c CVE-2022-0657 \u203c\n\nThe 5 Stars Rating Funnel WordPress Plugin | RRatingg WordPress plugin before 1.2.54 does not properly sanitise, validate and escape lead ids before using them in a SQL statement via the rrtngg_delete_leads AJAX action, available to unauthenticated users, leading to an unauthenticated SQL injection issue. There is an attempt to sanitise the input, using sanitize_text_field(), however such function is not intended to prevent SQL injections.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-04-25T20:36:26.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/fa2b1dcd-7df5-4081-9620-889db3258efa/export</guid>
      <pubDate>Mon, 25 Apr 2022 20:36:26 +0000</pubDate>
    </item>
  </channel>
</rss>
