Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-2442Published · Updated

Action summary

Affected: ≤2.0.7Update to 2.0.8 or newer

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-93 Improper Neutralization of CRLF Sequences
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Page Builder: Pagelayer – Drag and Drop website builder pagelayer

  1. Affected≤ 2.0.7
  2. Patched in2.0.8

Update to 2.0.8 or newer.

You are affected if you run ≤ 2.0.7. Version 2.0.8 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Page Builder: Pagelayer – Drag and Drop website builder.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.0.8, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Page Builder: Pagelayer – Drag and Drop website builder to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Drew Webber (mcdruid).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Page Builder: Pagelayer – Drag and Drop website builder

All 30
More vulnerabilities in Page Builder: Pagelayer – Drag and Drop website builder
SeverityVulnerabilityCVEPublished
Medium4.3Incorrect Authorization to Authenticated (Contributor+) Mail Relay Configuration via 'contacts'
≤2.0.9Update to 2.1.0
CVE-2026-2470
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via Anchor Block
≤2.0.9Update to 2.1.0
CVE-2026-3297
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via Button Widget Custom Attributes
≤2.0.8Update to 2.0.9
CVE-2026-2509
Medium4.3Authenticated (Contributor+) Information Exposure
≤2.0.8Update to 2.0.9
CVE-2026-39469
Medium4.3Authenticated (Author+) Insecure Direct Object Reference
≤2.0.5Update to 2.0.6
CVE-2025-12366

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?