<?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 01:09:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-5167 — CM Email Registration Blacklist and Whitelist &lt; 1.4.9 - Add/Delete Emails via CSRF Add and delete any item from blackli…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-5167</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Unknown CM Email Registration Blacklist and Whitelist, creativemindssolutions cm_email_registration_blacklist_and_whitelist&lt;/p&gt;
&lt;p&gt;The CM Email Registration Blacklist and Whitelist WordPress plugin before 1.4.9 does not have CSRF check when adding or deleting an item from the blacklist or whitelist, which could allow attackers to make a logged in admin add or delete settings from the blacklist or whitelist menu via a CSRF attack&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Unknown CM Email Registration Blacklist and Whitelist, creativemindssolutions cm_email_registration_blacklist_and_whitelist&lt;/p&gt;
&lt;p&gt;The CM Email Registration Blacklist and Whitelist WordPress plugin before 1.4.9 does not have CSRF check when adding or deleting an item from the blacklist or whitelist, which could allow attackers to make a logged in admin add or delete settings from the blacklist or whitelist menu via a CSRF attack&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-5167</guid>
    </item>
  </channel>
</rss>
