<?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>Wed, 06 May 2026 10:53:08 +0000</lastBuildDate>
    <item>
      <title>af678057-8e44-43bc-926d-cb8b2436319d</title>
      <link>https://db.gcve.eu/sighting/af678057-8e44-43bc-926d-cb8b2436319d/export</link>
      <description>{"uuid": "af678057-8e44-43bc-926d-cb8b2436319d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-24504", "type": "seen", "source": "https://t.me/cibsecurity/26669", "content": "\u203c CVE-2021-24504 \u203c\n\nThe WP LMS \u00c3\u00a2\u00e2\u201a\u00ac\u00e2\u20ac\u0153 Best WordPress LMS Plugin WordPress plugin through 1.1.2 does not properly sanitise or validate its User Field Titles, allowing XSS payload to be used in them. Furthermore, no CSRF and capability checks were in place, allowing such attack to be performed either via CSRF or as any user (including unauthenticated)\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-08-02T14:27:41.000000Z"}</description>
      <content:encoded>{"uuid": "af678057-8e44-43bc-926d-cb8b2436319d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-24504", "type": "seen", "source": "https://t.me/cibsecurity/26669", "content": "\u203c CVE-2021-24504 \u203c\n\nThe WP LMS \u00c3\u00a2\u00e2\u201a\u00ac\u00e2\u20ac\u0153 Best WordPress LMS Plugin WordPress plugin through 1.1.2 does not properly sanitise or validate its User Field Titles, allowing XSS payload to be used in them. Furthermore, no CSRF and capability checks were in place, allowing such attack to be performed either via CSRF or as any user (including unauthenticated)\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-08-02T14:27:41.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/af678057-8e44-43bc-926d-cb8b2436319d/export</guid>
      <pubDate>Mon, 02 Aug 2021 14:27:41 +0000</pubDate>
    </item>
  </channel>
</rss>
