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

5.3
Improper Neutralization of CRLF Sequences ('CRLF Injection')
CVE CVE-2026-12127
CVSS 5.3 (Medium)
Publicly Published June 30, 2026
Last Updated July 1, 2026
Researcher AlexHenry - Black Lantern Security

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.

References

Share

Vulnerability Details for WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More

Software Type Plugin
Software Slug wpforms-lite (view on wordpress.org)
Patched? Yes
Remediation Update to version 1.10.2.1, or a newer patched version
Affected Version
  • <= 1.10.2
Patched Version
  • 1.10.2.1

Recent vulnerabilities in WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More

# Title CVE ID CVSS Researchers Date
1 WPForms <= 2.0.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via OptinMonster Integration data-sitekey Attribute in Post Content CVE-2026-15782 4.9 Asaf Mozes July 20, 2026
2 WPForms <= 1.10.0.4 - Unauthenticated Insufficient Verification of Data Authenticity via PayPal Commerce Webhook Endpoint CVE-2026-7792 5.3 Valatty June 5, 2026
3 WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More <= 1.10.0.4 - Missing Authorization CVE-2026-48835 5.3 Cyrille COQUARD May 28, 2026
4 Contact Form by WPForms <= 1.10.0.2 - Cross-Site Request Forgery CVE-2026-40764 4.3 vladimir tokarev March 31, 2026
5 WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More <= 1.9.8.7 - Unauthenticated Sensitive Information Exposure CVE-2026-25339 5.3 Sandeep V March 23, 2026
6 Contact Form by WPForms <= 1.9.9.3 - Missing Authorization CVE-2026-32446 4.3 davidfdzmorilla March 7, 2026
7 WPForms Lite <= 1.9.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'start_timestamp' Parameter CVE-2025-3794 5.4 Asaf Mozes May 9, 2025
8 WPForms Lite <= 1.9.3.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via fieldHTML Parameter CVE-2024-13403 6.4 Asaf Mozes February 3, 2025
9 Contact Form by WPForms <= 1.9.2.2 - Missing Authorization CVE-2024-56276 4.3 Rafie Muhammad January 3, 2025
10 WPForms 1.8.4 - 1.9.2.1 - Missing Authorization to Authenticated (Subscriber+) Payment Refund and Subscription Cancellation CVE-2024-11205 8.5 villu164 December 9, 2024

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation