CVE-2026-2442

Pagelayer <= 2.0.7 - Improper Neutralization of CRLF Sequences to Unauthenticated Email Header Injection via 'email'

2026-03-27 20:45
Drew Webber (mcdruid)

Strategic Overview

Status
Patched in 2.0.8
Affected Version
<= 2.0.7
CVSS
5.3Medium
Weakness type
CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')
CVE
CVE-2026-2442
View all Page Builder: Pagelayer – Drag and Drop website builder vulnerabilities

At a glance

CVE-2026-2442 is a medium-severity Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting versions <= 2.0.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.8; sites on affected versions should update now. Disclosed March 2026, reported by Drew Webber (mcdruid).

Vulnerability Overview

The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences ('CRLF Injection') 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 'email' parameter granted they can target a contact form configured to use placeholders in mail template headers.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')

The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

Remediation

Update to version 2.0.8, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Page Builder: Pagelayer 2.0.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C