<?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>Fri, 09 Oct 2026 06:24:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-284715</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-284715</link>
      <description>EUVD-2026-284715</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-284715</guid>
    </item>
    <item>
      <title>fkie_cve-2024-11197</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-11197</link>
      <description>&lt;p&gt;The Lock User Account plugin for WordPress is vulnerable to user lock bypass in all versions up to, and including, 1.0.5. This is due to permitting application password logins when user accounts are locked. This makes it possible for authenticated attackers, with existing application passwords, to interact with the vulnerable site via an API such as XML-RPC or REST despite their account being locked.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Lock User Account plugin for WordPress is vulnerable to user lock bypass in all versions up to, and including, 1.0.5. This is due to permitting application password logins when user accounts are locked. This makes it possible for authenticated attackers, with existing application passwords, to interact with the vulnerable site via an API such as XML-RPC or REST despite their account being locked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-11197</guid>
    </item>
  </channel>
</rss>
