CVE-2026-2442: CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection') in softaculous Page Builder: Pagelayer – Drag and Drop website builder
CVE-2026-2442 is a medium severity vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting all versions up to 2. 0. 7. It involves improper neutralization of CRLF sequences in the contact form handler, allowing unauthenticated attackers to inject arbitrary email headers via the 'email' parameter. This can lead to email header injection, enabling attackers to manipulate email delivery, such as adding Bcc or Cc recipients. Exploitation requires targeting a contact form configured to use placeholders in mail template headers. The vulnerability does not impact confidentiality or availability but can affect email integrity and potentially facilitate spam or phishing campaigns. No known exploits are currently reported in the wild. Mitigation involves sanitizing input to remove CRLF characters before header insertion and updating the plugin once a patch is available. Countries with significant WordPress usage and reliance on this plugin are at higher risk, including the United States, India, Brazil, Germany, and the United Kingdom.
AI Analysis
Technical Summary
CVE-2026-2442 is a CRLF injection vulnerability classified under CWE-93, found in the Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress. The issue arises because the plugin's contact form handler performs placeholder substitution on attacker-controlled form fields and subsequently inserts these values directly into email headers without sanitizing or removing carriage return (CR) and line feed (LF) characters. This improper neutralization allows an unauthenticated attacker to inject arbitrary email headers, such as Bcc or Cc, by manipulating the 'email' parameter in the contact form. The vulnerability affects all versions up to and including 2.0.7. Exploitation requires that the targeted contact form is configured to use placeholders in mail template headers, which is a common configuration in many WordPress contact forms. The injected headers can be used to manipulate email delivery, potentially enabling spam relay, phishing, or other malicious email activities. The CVSS v3.1 base score is 5.3, reflecting medium severity due to the lack of confidentiality or availability impact and the ease of exploitation without authentication or user interaction. No patches or known exploits in the wild have been reported as of the publication date. The vulnerability highlights the importance of proper input validation and sanitization in web applications, especially when user input is incorporated into email headers.
Potential Impact
The primary impact of this vulnerability is on the integrity of email communications sent via the vulnerable contact forms. Attackers can inject additional email headers, potentially allowing them to add Bcc or Cc recipients, which can be exploited to send spam or phishing emails from legitimate websites. This can damage the reputation of affected organizations and lead to blacklisting of their email domains. Although confidentiality and availability are not directly impacted, the abuse of email functionality can indirectly affect business operations and trust. Organizations relying on the affected plugin for customer communications may face increased risk of email-based attacks and reputational harm. Since exploitation does not require authentication or user interaction, the attack surface is broad, especially for publicly accessible contact forms. The lack of known exploits in the wild suggests limited active exploitation currently, but the vulnerability remains a significant risk until patched.
Mitigation Recommendations
Organizations should immediately review their use of the Page Builder: Pagelayer plugin and identify any contact forms configured with placeholders in mail template headers. Until an official patch is released, administrators should consider disabling or restricting the affected contact forms to prevent exploitation. Implement input validation and sanitization routines that explicitly remove or encode CR and LF characters from user-supplied input used in email headers. Employ web application firewalls (WAFs) with rules designed to detect and block CRLF injection attempts targeting email headers. Monitor outgoing email logs for unusual header patterns or unexpected recipients that may indicate exploitation attempts. Stay informed about updates from the plugin vendor and apply patches promptly once available. Additionally, consider using alternative contact form plugins with robust security practices if immediate patching is not feasible. Regular security audits and penetration testing focusing on email injection vulnerabilities can help detect similar issues proactively.
Affected Countries
United States, India, Brazil, Germany, United Kingdom, Canada, Australia, France, Italy, Spain
CVE-2026-2442: CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection') in softaculous Page Builder: Pagelayer – Drag and Drop website builder
Description
CVE-2026-2442 is a medium severity vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting all versions up to 2. 0. 7. It involves improper neutralization of CRLF sequences in the contact form handler, allowing unauthenticated attackers to inject arbitrary email headers via the 'email' parameter. This can lead to email header injection, enabling attackers to manipulate email delivery, such as adding Bcc or Cc recipients. Exploitation requires targeting a contact form configured to use placeholders in mail template headers. The vulnerability does not impact confidentiality or availability but can affect email integrity and potentially facilitate spam or phishing campaigns. No known exploits are currently reported in the wild. Mitigation involves sanitizing input to remove CRLF characters before header insertion and updating the plugin once a patch is available. Countries with significant WordPress usage and reliance on this plugin are at higher risk, including the United States, India, Brazil, Germany, and the United Kingdom.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-2442 is a CRLF injection vulnerability classified under CWE-93, found in the Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress. The issue arises because the plugin's contact form handler performs placeholder substitution on attacker-controlled form fields and subsequently inserts these values directly into email headers without sanitizing or removing carriage return (CR) and line feed (LF) characters. This improper neutralization allows an unauthenticated attacker to inject arbitrary email headers, such as Bcc or Cc, by manipulating the 'email' parameter in the contact form. The vulnerability affects all versions up to and including 2.0.7. Exploitation requires that the targeted contact form is configured to use placeholders in mail template headers, which is a common configuration in many WordPress contact forms. The injected headers can be used to manipulate email delivery, potentially enabling spam relay, phishing, or other malicious email activities. The CVSS v3.1 base score is 5.3, reflecting medium severity due to the lack of confidentiality or availability impact and the ease of exploitation without authentication or user interaction. No patches or known exploits in the wild have been reported as of the publication date. The vulnerability highlights the importance of proper input validation and sanitization in web applications, especially when user input is incorporated into email headers.
Potential Impact
The primary impact of this vulnerability is on the integrity of email communications sent via the vulnerable contact forms. Attackers can inject additional email headers, potentially allowing them to add Bcc or Cc recipients, which can be exploited to send spam or phishing emails from legitimate websites. This can damage the reputation of affected organizations and lead to blacklisting of their email domains. Although confidentiality and availability are not directly impacted, the abuse of email functionality can indirectly affect business operations and trust. Organizations relying on the affected plugin for customer communications may face increased risk of email-based attacks and reputational harm. Since exploitation does not require authentication or user interaction, the attack surface is broad, especially for publicly accessible contact forms. The lack of known exploits in the wild suggests limited active exploitation currently, but the vulnerability remains a significant risk until patched.
Mitigation Recommendations
Organizations should immediately review their use of the Page Builder: Pagelayer plugin and identify any contact forms configured with placeholders in mail template headers. Until an official patch is released, administrators should consider disabling or restricting the affected contact forms to prevent exploitation. Implement input validation and sanitization routines that explicitly remove or encode CR and LF characters from user-supplied input used in email headers. Employ web application firewalls (WAFs) with rules designed to detect and block CRLF injection attempts targeting email headers. Monitor outgoing email logs for unusual header patterns or unexpected recipients that may indicate exploitation attempts. Stay informed about updates from the plugin vendor and apply patches promptly once available. Additionally, consider using alternative contact form plugins with robust security practices if immediate patching is not feasible. Regular security audits and penetration testing focusing on email injection vulnerabilities can help detect similar issues proactively.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-13T01:21:59.845Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c7a4822b68dbd88ed883f8
Added to database: 3/28/2026, 9:50:58 AM
Last enriched: 3/28/2026, 10:06:02 AM
Last updated: 3/28/2026, 10:55:21 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.