<?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-08T08:11:15.417929+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-23979</id>
    <title>EUVD-2026-23979</title>
    <updated>2026-10-08T08:11:15.420440+00:00</updated>
    <content>EUVD-2026-23979</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-23979"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-24584</id>
    <title>fkie_cve-2021-24584</title>
    <updated>2026-10-08T08:11:15.420473+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The Timetable and Event Schedule WordPress plugin before 2.4.2 does not have proper access control when updating a timeslot, allowing any user with the edit_posts capability (contributor+) to update arbitrary timeslot from any events. Furthermore, no CSRF check is in place as well, allowing such attack to be perform via CSRF against a logged in with such capability. In versions before 2.3.19, the lack of sanitisation and escaping in some of the fields, like the descritption could also lead to Stored XSS issues</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-24584"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2v92-7cf3-4vm5</id>
    <title>GHSA-2v92-7cf3-4vm5</title>
    <updated>2026-10-08T08:11:15.420506+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The Timetable and Event Schedule WordPress plugin before 2.4.2 does not have proper access control when updating a timeslot, allowing any user with the edit_posts capability (contributor+) to update arbitrary timeslot from any events. Furthermore, no CSRF check is in place as well, allowing such attack to be perform via CSRF against a logged in with such capability. In versions before 2.3.19, the lack of sanitisation and escaping in some of the fields, like the descritption could also lead to Stored XSS issues</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2v92-7cf3-4vm5"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-24584</id>
    <title>gsd-2021-24584</title>
    <updated>2026-10-08T08:11:15.420525+00:00</updated>
    <content>gsd-2021-24584</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-24584"/>
  </entry>
</feed>
