<?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>Fri, 19 Jun 2026 17:47:35 +0000</lastBuildDate>
    <item>
      <title>8e40c661-6e2a-439a-a611-e4f7cc0e9ab7</title>
      <link>https://vulnerability.circl.lu/sighting/8e40c661-6e2a-439a-a611-e4f7cc0e9ab7/export</link>
      <description>{"uuid": "8e40c661-6e2a-439a-a611-e4f7cc0e9ab7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-25102", "type": "seen", "source": "https://t.me/cibsecurity/41733", "content": "\u203c CVE-2021-25102 \u203c\n\nThe All In One WP Security &amp;amp; Firewall WordPress plugin before 4.4.11 does not validate, sanitise and escape the redirect_to parameter before using it to redirect user, either via a Location header, or meta url attribute, when the Rename Login Page is active, which could lead to an Arbitrary Redirect as well as Cross-Site Scripting issue. Exploitation of this issue requires the Login Page URL value to be known, which should be hard to guess, reducing the risk\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-05-02T20:27:57.000000Z"}</description>
      <content:encoded>{"uuid": "8e40c661-6e2a-439a-a611-e4f7cc0e9ab7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-25102", "type": "seen", "source": "https://t.me/cibsecurity/41733", "content": "\u203c CVE-2021-25102 \u203c\n\nThe All In One WP Security &amp;amp; Firewall WordPress plugin before 4.4.11 does not validate, sanitise and escape the redirect_to parameter before using it to redirect user, either via a Location header, or meta url attribute, when the Rename Login Page is active, which could lead to an Arbitrary Redirect as well as Cross-Site Scripting issue. Exploitation of this issue requires the Login Page URL value to be known, which should be hard to guess, reducing the risk\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-05-02T20:27:57.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/8e40c661-6e2a-439a-a611-e4f7cc0e9ab7/export</guid>
      <pubDate>Mon, 02 May 2022 20:27:57 +0000</pubDate>
    </item>
  </channel>
</rss>
