Responsive Blocks <= 2.2.0 - Unauthenticated Open Email Relay via REST API 'email_to' Parameter
Strategic Overview
- Status
- Patched in 2.2.1
- Affected Plugin
- Responsive Blocks – Page Builder for Blocks & Patterns
- Affected Version
<= 2.2.0- CVSS
- 5.3Medium
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE-2026-6675
At a glance
CVE-2026-6675 is a medium-severity Improper Input Validation vulnerability in the Responsive Blocks WordPress plugin, affecting versions <= 2.2.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed April 2026, reported by Even Stokkedalen.
Vulnerability Overview
The Responsive Blocks – Page Builder for Blocks & Patterns plugin for WordPress is vulnerable to Unauthenticated Open Email Relay in all versions up to, and including, 2.2.0. This is due to insufficient authorization checks and missing server-side validation of the recipient email address supplied via a public REST API route. This makes it possible for unauthenticated attackers to send arbitrary emails to any recipient of their choosing through the affected WordPress site's mail server, effectively turning the site into an open mail relay.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-20: Improper Input Validation
Reaching this weakness in Responsive Blocks <= 2.2.0 takes no account at all. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.
The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Responsive Blocks the fix is 2.2.1: builds <= 2.2.0 are affected, anything from 2.2.1 onward is not.
Remediation
Update to version 2.2.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Responsive Blocks 2.2.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Responsive Blocks – Page Builder for Blocks & Patterns
- 6.4CVE-2025-53202: Responsive Blocks <= 2.0.6 Stored Cross-Site Scripting
CVE-2025-53202 - 6.4CVE-2025-49881: Responsive Blocks <= 2.0.5 Stored Cross-Site Scripting
CVE-2025-49881 - 6.4CVE-2025-39578: Responsive Blocks <= 2.0.2 Stored Cross-Site Scripting
CVE-2025-39578 - 6.4CVE-2025-22697: Responsive Blocks <= 1.9.9 Stored Cross-Site Scripting
CVE-2025-22697 - 6.4CVE-2024-13732: Responsive Blocks Stored XSS
CVE-2024-13732 - 6.4CVE-2024-12268: Responsive Blocks Stored XSS
CVE-2024-12268 - 6.4CVE-2024-43335: Responsive Blocks Stored XSS
CVE-2024-43335 - 5.3CVE-2026-32543: Responsive Blocks Missing Authorization
CVE-2026-32543
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C