CVE-2026-12127
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 46% of all known CVEs.
References
Related Vulnerabilities
Other CWE-93 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-61884 | High | 7.5 | 98% | KEV + Ransom | - |
| CVE-2022-0666 | High | 7.5 | 44% | - | Fix |
| CVE-2016-3115 | Medium | 6.4 | 37% | - | Fix |
| CVE-2024-20337 | High | 8.2 | 30% | - | Fix |
| CVE-2021-39172 | High | 8.8 | 29% | - | Fix |
| CVE-2016-4975 | Medium | 6.1 | 20% | - | Fix |
Common questions
How do I fix CVE-2026-12127?
No published fix for CVE-2026-12127 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-12127 being actively exploited?
Not that we know of. CVE-2026-12127 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.60% is the estimated probability that it will be exploited in the next 30 days. That is higher than 46% of all scored CVEs.
How severe is CVE-2026-12127?
CVE-2026-12127 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-12127
Markdown
[](https://tridentstack.com/cve/CVE-2026-12127)HTML
<a href="https://tridentstack.com/cve/CVE-2026-12127"><img src="https://tridentstack.com/cve/badge/CVE-2026-12127.svg" alt="CVE-2026-12127"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-01.