Security readout for executives and security teams
Plain-English summary
CVE-2026-2442 affects the Pagelayer WordPress page builder plugin through version 2.0.7. An unauthenticated attacker may be able to inject additional email headers through a contact form email field when the form is configured to place user-controlled placeholders into mail template headers.
Executive priority
Prioritize remediation for public WordPress sites that use Pagelayer contact forms, because exploitation is unauthenticated and can abuse trusted site email delivery. Overall priority is moderate due to limited integrity impact and no provided evidence of active exploitation.
Technical view
The vulnerability is a CRLF injection issue in the Pagelayer contact form handler. Attacker-controlled form fields can be substituted into email header templates without removing carriage return or line feed characters, allowing header manipulation such as adding additional recipients. The source bundle maps this to CWE-93 and CVSS 3.1 score 5.3 with vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
Likely exposure
Internet-facing WordPress sites using Page Builder: Pagelayer - Drag and Drop website builder version 2.0.7 or earlier are the likely exposure group, especially if they publish Pagelayer contact forms configured to use placeholders in email template headers.
Exploitation context
The provided sources describe unauthenticated network exploitation against a vulnerable contact form configuration. The bundle does not indicate CISA KEV listing or active exploitation, so active exploitation should not be assumed from this evidence.
Researcher notes
The source bundle states affected versions as all versions up to and including 2.0.7, while the structured affected entry contains an unhelpful version value of "0" with defaultStatus "unaffected". Treat the narrative description and references as the actionable affected-range evidence. Patch details should be verified against vendor or WordPress plugin changelog evidence before declaring a specific fixed version.
Mitigation direction
- Inventory WordPress sites for the Pagelayer plugin and identify any installations running version 2.0.7 or earlier.
- Update Pagelayer according to vendor guidance or to a release confirmed to include the referenced WordPress Trac fix; if patch evidence is unclear, verify the vendor changelog before relying on the update.
- Review Pagelayer contact forms and remove user-controlled placeholders from email header fields where possible.
- If immediate patching is not possible, disable affected contact forms or route them through a safer form handling path until the plugin is remediated.
- Review outbound mail configuration and monitoring for unexpected additional recipients or abnormal form-generated mail volume.
Validation and detection
- Confirm the installed Pagelayer version on each WordPress site and compare it against the affected range stated in the source bundle.
- Identify whether any Pagelayer contact form uses placeholders in mail template header fields such as recipient, reply-to, cc, or bcc-related settings.
- After remediation, verify that user-supplied form values cannot change generated email headers and that CR/LF characters are rejected, removed, or safely handled.
- Review mail logs for form-generated messages with unexpected recipients or header anomalies during the suspected exposure window.
- Document the remediation version or vendor advisory evidence used for closure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-93: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2442 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of CRLF Sequences ('CRLF Injection')
Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.