CVE-2026-12127
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk26th percentile - higher than 26% of all known CVEs
Summary
The WPForms plugin for WordPress up to version 1.10.2 is vulnerable to CRLF Injection, allowing email header injection. The flaw occurs due to improper handling of the Reply-To display name, enabling unauthenticated attackers to inject arbitrary headers like Bcc into outgoing notification emails.
Risk Assessment
An attacker can silently blind-copy notification emails to an attacker-controlled address, leading to potential data leakage of sensitive information submitted via forms (e.g., personal data, inquiries).
Recommendation
Immediately update the WPForms plugin to the latest available version that fixes this vulnerability. If an update is not possible, temporarily disable the use of Paragraph Text (textarea) fields as the Reply-To display name in notifications.
Other vulnerabilities in WPForms
See all- CVE-2026-15782Medium
WPForms plugin for WordPress up to 2.0.0.1 has a Stored XSS vulnerability via the data-sitekey attribute of OptinMonster integration. Authenticated attackers with contributor-level access can inject scripts that execute on page view.
- CVE-2026-48835High
In WPForms versions <= 1.10.0.4, there is an issue with unauthenticated access to the contact form, leading to broken access control.
- CVE-2026-4986Medium
The WPForms WordPress plugin before version 1.10.0.5 does not verify the authenticity of incoming PayPal webhook events before processing them, allowing unauthenticated attackers to forge webhook payloads and manipulate the payment state of arbitrary transactions.
- CVE-2026-7792Medium
The WPForms plugin for WordPress up to version 1.10.0.1 does not properly verify the authenticity of PayPal Commerce webhooks. Unauthenticated attackers can forge webhook events and modify payment records, e.g., reactivate a cancelled subscription.
Original NVD description (English source)
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.