<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T12:15:58.888319+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-24469</id>
    <title>EUVD-2026-24469</title>
    <updated>2026-10-08T12:15:58.968127+00:00</updated>
    <content>EUVD-2026-24469</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-24469"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-25106</id>
    <title>fkie_cve-2021-25106</title>
    <updated>2026-10-08T12:15:58.968171+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The Privacy Policy Generator, Terms &amp; Conditions Generator WordPress Plugin : WPLegalPages WordPress plugin before 2.7.1 does not check for authorisation and has a flawed CSRF logic when saving its settings, allowing any authenticated users, such as subscriber, to update them. Furthermore, due to the lack of sanitisation and escaping, it could lead to Stored Cross-Site Scripting</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-25106"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-h2hg-rvg6-p5x3</id>
    <title>GHSA-h2hg-rvg6-p5x3</title>
    <updated>2026-10-08T12:15:58.968209+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The Privacy Policy Generator, Terms &amp; Conditions Generator WordPress Plugin : WPLegalPages WordPress plugin before 2.7.1 does not check for authorisation and has a flawed CSRF logic when saving its settings, allowing any authenticated users, such as subscriber, to update them. Furthermore, due to the lack of sanitisation and escaping, it could lead to Stored Cross-Site Scripting</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-h2hg-rvg6-p5x3"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-25106</id>
    <title>gsd-2021-25106</title>
    <updated>2026-10-08T12:15:58.968230+00:00</updated>
    <content>gsd-2021-25106</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-25106"/>
  </entry>
</feed>
