CVE-2026-12127: WPForms <= 1.10.2 - Improper Neutralization of CRLF Sequences to Unauthenticated Email Header Injection via Reply-To Display Name

Published Jul 1, 2026
·
Updated

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 getreplytoaddress() processing the Reply-To display name through smart-tag expansion with context 'notification' instead of 'notification-reply-to', which bypasses email-address validation while wpformssanitizetextareafield() 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.

Affected Software

1 affected component
WPForms WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More<=1.10.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More to a version that resolves this vulnerability.

    Fixed in 1.10.2
  2. Configuration

    Do not configure the Reply-To display name to use a Paragraph Text (textarea) field as the Reply-To display name via a Smart Tag, since this can inject CRLF sequences into the display name that is concatenated into the raw Reply-To mail header string.

    WPForms notifications (Smart Tags for Reply-To display name) Reply-To display name smart tag field type/usage = Paragraph Text (textarea) via Smart Tag (do not configure)

Event History

Jul 1, 2026
CVE Published
via MITRE·04:32 AM
Data Sourced
via MITRE·04:32 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-12127?

The severity of CVE-2026-12127 is classified as medium with a base score of 5.3.

2

What kind of vulnerability is CVE-2026-12127?

CVE-2026-12127 is an Improper Neutralization of CRLF Sequences vulnerability, commonly known as CRLF Injection.

3

How do I fix CVE-2026-12127?

To fix CVE-2026-12127, update the WPForms plugin to a version higher than 1.10.2.

4

What software is affected by CVE-2026-12127?

CVE-2026-12127 affects all versions of the WPForms plugin for WordPress up to and including version 1.10.2.

5

What can an attacker achieve with CVE-2026-12127?

An attacker can exploit CVE-2026-12127 to perform unauthorized email header injection via the Reply-To display name.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203