<?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 entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 17:17:22 +0000</lastBuildDate>
    <item>
      <title>cnvd-2022-59805</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-59805</link>
      <description>cnvd-2022-59805</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-59805</guid>
    </item>
    <item>
      <title>EUVD-2026-24550</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-24550</link>
      <description>EUVD-2026-24550</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-24550</guid>
    </item>
    <item>
      <title>fkie_cve-2021-25102</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-25102</link>
      <description>&lt;p&gt;The 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&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The 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&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-25102</guid>
    </item>
    <item>
      <title>GHSA-jw24-79q4-qcv5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jw24-79q4-qcv5</link>
      <description>&lt;p&gt;The 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&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The 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&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jw24-79q4-qcv5</guid>
    </item>
    <item>
      <title>gsd-2021-25102</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-25102</link>
      <description>gsd-2021-25102</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-25102</guid>
    </item>
  </channel>
</rss>
