<?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>Wed, 07 Oct 2026 05:14:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-2442 — Pagelayer &lt;= 2.0.7 - Improper Neutralization of CRLF Sequences to Unauthenticated Email Header Injection via 'email'</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-2442</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; softaculous Page Builder: Pagelayer – Drag and Drop website builder&lt;/p&gt;
&lt;p&gt;The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences (&amp;#39;CRLF Injection&amp;#39;) in all versions up to, and including, 2.0.7. This is due to the contact form handler performing placeholder substitution on attacker-controlled form fields and then passing the resulting values into email headers without removing CR/LF characters. This makes it possible for unauthenticated attackers to inject arbitrary email headers (for example Bcc / Cc) and abuse form email delivery via the &amp;#39;email&amp;#39; parameter granted they can target a contact form configured to use placeholders in mail template headers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; softaculous Page Builder: Pagelayer – Drag and Drop website builder&lt;/p&gt;
&lt;p&gt;The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences (&amp;#39;CRLF Injection&amp;#39;) in all versions up to, and including, 2.0.7. This is due to the contact form handler performing placeholder substitution on attacker-controlled form fields and then passing the resulting values into email headers without removing CR/LF characters. This makes it possible for unauthenticated attackers to inject arbitrary email headers (for example Bcc / Cc) and abuse form email delivery via the &amp;#39;email&amp;#39; parameter granted they can target a contact form configured to use placeholders in mail template headers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-2442</guid>
    </item>
  </channel>
</rss>
