<?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, 23 Oct 2026 23:18:52 +0000</lastBuildDate>
    <item>
      <title>cnvd-2022-88246</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-88246</link>
      <description>cnvd-2022-88246</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-88246</guid>
    </item>
    <item>
      <title>EUVD-2026-240850</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-240850</link>
      <description>EUVD-2026-240850</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-240850</guid>
    </item>
    <item>
      <title>fkie_cve-2022-2987</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-2987</link>
      <description>&lt;p&gt;The Ldap WP Login / Active Directory Integration WordPress plugin before 3.0.2 does not have any authorisation and CSRF checks when updating it&amp;#39;s settings (which are hooked to the init action), allowing unauthenticated attackers to update them. Attackers could set their own LDAP server to be used to authenticated users, therefore bypassing the current authentication&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Ldap WP Login / Active Directory Integration WordPress plugin before 3.0.2 does not have any authorisation and CSRF checks when updating it&amp;#39;s settings (which are hooked to the init action), allowing unauthenticated attackers to update them. Attackers could set their own LDAP server to be used to authenticated users, therefore bypassing the current authentication&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-2987</guid>
    </item>
    <item>
      <title>GHSA-mh2q-2wc7-4q2g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mh2q-2wc7-4q2g</link>
      <description>&lt;p&gt;The Ldap WP Login / Active Directory Integration WordPress plugin before 3.0.2 does not have any authorisation and CSRF checks when updating it&amp;#39;s settings (which are hooked to the init action), allowing unauthenticated attackers to update them. Attackers could set their own LDAP server to be used to authenticated users, therefore bypassing the current authentication&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Ldap WP Login / Active Directory Integration WordPress plugin before 3.0.2 does not have any authorisation and CSRF checks when updating it&amp;#39;s settings (which are hooked to the init action), allowing unauthenticated attackers to update them. Attackers could set their own LDAP server to be used to authenticated users, therefore bypassing the current authentication&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mh2q-2wc7-4q2g</guid>
    </item>
    <item>
      <title>gsd-2022-2987</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-2987</link>
      <description>gsd-2022-2987</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-2987</guid>
    </item>
  </channel>
</rss>
