https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 23:27:26 +0000 https://cve.radiocsirt.org/vuln/cve-2026-12127 <p><strong>Affected:</strong> smub WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz &amp; More</p> <p>The WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, &amp; More plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences (&#39;CRLF Injection&#39;) 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 `&#39;notification&#39;` instead of `&#39;notification-reply-to&#39;`, 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.</p> <p><strong>Affected:</strong> smub WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz &amp; More</p> <p>The WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, &amp; More plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences (&#39;CRLF Injection&#39;) 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 `&#39;notification&#39;` instead of `&#39;notification-reply-to&#39;`, 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.</p> https://cve.radiocsirt.org/vuln/cve-2026-12127