{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12127 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12127 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12127 is a medium-severity vulnerability in smub WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz \u0026 More, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12127 and fix it if it is affected.\n\nWhat it is: CVE-2026-12127 is a medium-severity vulnerability in smub WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz \u0026 More, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12127 in the wild and no public exploit code.\n\nAffected product: smub WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz \u0026 More. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-12127/ (Markdown: https://insights.sbomify.com/CVE-2026-12127/index.md)","id":"CVE-2026-12127","markdown":"https://insights.sbomify.com/CVE-2026-12127/index.md","name":"CVE-2026-12127","record":{"aliases":["GHSA-95c2-pg6v-7hqp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject email headers into WPForms notifications if a textarea field is used for the Reply-To display name, allowing silent BCC to attacker addresses.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"The WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz \u0026 More","id":"CVE-2026-12127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":11,"next":{"headline":"Business logic in Pinpoint Booking System – Version 2","id":"CVE-2026-12128"},"packages":[],"prev":{"headline":"WCFM Marketplace \u003c= 3.7.3 - Authenticated (Vendor+) Stored Cross-Site Scripting via Attachment 'post_title'","id":"CVE-2026-12126"},"products":["WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz \u0026 More"],"published":"2026-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["smub"]},"summary":"Unauthenticated attackers can inject email headers into WPForms notifications if a textarea field is used for the Reply-To display name, allowing silent BCC to attacker addresses.","url":"https://insights.sbomify.com/CVE-2026-12127/"}