CVE-2026-12127: CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection') in smub WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More
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.
AI Analysis
Technical Summary
The WPForms plugin for WordPress, up to and including version 1.10.2, suffers from a CRLF injection vulnerability (CWE-93) in the get_reply_to_address() function. The issue arises because the Reply-To display name is processed with the 'notification' context instead of 'notification-reply-to', bypassing email address validation. Additionally, the sanitization function wpforms_sanitize_textarea_field() preserves CR/LF characters, which are concatenated directly into the raw Reply-To mail header. This allows unauthenticated attackers to inject arbitrary email headers such as Bcc into notification emails, enabling silent blind-copying of notifications to attacker-controlled addresses. Exploitation requires that the form notification uses a Paragraph Text (textarea) field as the Reply-To display name via a Smart Tag.
Potential Impact
An unauthenticated attacker can inject additional email headers into outgoing notification emails, such as Bcc, allowing them to silently receive copies of these emails. This compromises the confidentiality of notification emails but does not affect their availability or integrity. There is no indication of direct code execution or system compromise from this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid configuring form notifications to use a Paragraph Text (textarea) field as the Reply-To display name via Smart Tags. Monitor vendor communications for updates and apply official patches once released.
CVE-2026-12127: CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection') in smub WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More
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.
CVSS v3.1
Score 5.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The WPForms plugin for WordPress, up to and including version 1.10.2, suffers from a CRLF injection vulnerability (CWE-93) in the get_reply_to_address() function. The issue arises because the Reply-To display name is processed with the 'notification' context instead of 'notification-reply-to', bypassing email address validation. Additionally, the sanitization function wpforms_sanitize_textarea_field() preserves CR/LF characters, which are concatenated directly into the raw Reply-To mail header. This allows unauthenticated attackers to inject arbitrary email headers such as Bcc into notification emails, enabling silent blind-copying of notifications to attacker-controlled addresses. Exploitation requires that the form notification uses a Paragraph Text (textarea) field as the Reply-To display name via a Smart Tag.
Potential Impact
An unauthenticated attacker can inject additional email headers into outgoing notification emails, such as Bcc, allowing them to silently receive copies of these emails. This compromises the confidentiality of notification emails but does not affect their availability or integrity. There is no indication of direct code execution or system compromise from this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid configuring form notifications to use a Paragraph Text (textarea) field as the Reply-To display name via Smart Tags. Monitor vendor communications for updates and apply official patches once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-06-12T15:16:37.220Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a44a07727e9c79719fbd4d4
Added to database: 07/01/2026, 05:07:03 UTC
Last enriched: 07/01/2026, 05:36:29 UTC
Last updated: 07/01/2026, 21:39:12 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.