Description
The WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences ('CRLF Injection') in all versions up to, and including, 1.10.2 This is due to `get_reply_to_address()` processing the Reply-To display name through smart-tag expansion with context `'notification'` instead of `'notification-reply-to'`, which bypasses email-address validation while `wpforms_sanitize_textarea_field()` intentionally preserves CR/LF characters that are never stripped before the display name is concatenated into the raw `Reply-To:` mail header string. This makes it possible for unauthenticated attackers to inject arbitrary additional email headers — such as `Bcc:` — into outgoing notification emails, silently blind-copying all notification email copies to an attacker-controlled address. Exploitation requires that a form notification is configured to use a Paragraph Text (textarea) field as the Reply-To display name via a Smart Tag.
Published: 2026-07-01
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability in the WPForms plug‑in allows attackers to inject arbitrary email headers through the Reply‑To display name field. The plug‑in incorrectly processes smart tags in the reply‑to field, bypassing validation and preserving CR/LF characters, which enables a CRLF injection that can add headers such as Bcc. This results in an attacker silently receiving copies of notification emails.

Affected Systems

Any WordPress site that runs WPForms version 1.10.2 or older, including all earlier releases of the plug‑in. Exploitation requires that a form contain a Paragraph Text (textarea) field configured as the Reply‑To display name via a smart tag.

Risk and Exploitability

This vulnerability has a CVSS score of 5.3, classifying it as medium severity. The EPSS score is currently unavailable, and it is not listed in the CISA KEV inventory. An attacker can exploit the flaw remotely by submitting data to a publicly accessible form that uses a textarea field as the reply‑to display name; no authentication is required. If the site has not been updated to 1.10.2 and the form is configured accordingly, each notification email will be silently BCC‑ed to an arbitrary address.

Generated by OpenCVE AI on July 1, 2026 at 12:57 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade WPForms to the latest version (>= 1.10.3).
  • Remove or disable any Paragraph Text fields that are configured as the Reply‑To email address or a different field type.
  • If the plugin settings allow, disable smart‑tag expansion in the Reply‑To field or replace the field type to eliminate CRLF injection risk.

Generated by OpenCVE AI on July 1, 2026 at 12:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 01 Jul 2026 12:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 01 Jul 2026 05:00:00 +0000

Type Values Removed Values Added
Description The WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences ('CRLF Injection') in all versions up to, and including, 1.10.2 This is due to `get_reply_to_address()` processing the Reply-To display name through smart-tag expansion with context `'notification'` instead of `'notification-reply-to'`, which bypasses email-address validation while `wpforms_sanitize_textarea_field()` intentionally preserves CR/LF characters that are never stripped before the display name is concatenated into the raw `Reply-To:` mail header string. This makes it possible for unauthenticated attackers to inject arbitrary additional email headers — such as `Bcc:` — into outgoing notification emails, silently blind-copying all notification email copies to an attacker-controlled address. Exploitation requires that a form notification is configured to use a Paragraph Text (textarea) field as the Reply-To display name via a Smart Tag.
Title WPForms <= 1.10.2 - Improper Neutralization of CRLF Sequences to Unauthenticated Email Header Injection via Reply-To Display Name
Weaknesses CWE-93
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-07-01T10:42:10.985Z

Reserved: 2026-06-12T15:16:37.220Z

Link: CVE-2026-12127

cve-icon Vulnrichment

Updated: 2026-07-01T10:33:37.928Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-01T13:00:15Z

Weaknesses
  • CWE-93

    Improper Neutralization of CRLF Sequences ('CRLF Injection')