CVE-2026-6703

Responsive Blocks <= 2.2.1 - Missing Authorization to Authenticated (Contributor+) Arbitrary Modification via AJAX Actions

2026-04-20 17:50
Even Stokkedalen

Strategic Overview

Status
Patched in 2.2.2
Affected Plugin
Responsive Blocks – Page Builder for Blocks & Patterns
Affected Version
2.0.9 – 2.2.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-6703
View all Responsive Blocks – Page Builder for Blocks & Patterns vulnerabilities

At a glance

CVE-2026-6703 is a medium-severity Missing Authorization vulnerability in the Responsive Blocks WordPress plugin, affecting versions 2.0.9 – 2.2.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.2.2; 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 unauthorized access in all versions up to, and including, 2.2.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to modify global site-wide plugin configuration options, including toggling custom CSS, disabling blocks, changing layout defaults such as content width, container padding, and container gap, and altering auto-block-recovery behavior.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Responsive Blocks 2.0.9 – 2.2.1 takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Responsive Blocks the fix is 2.2.2: builds 2.0.9 – 2.2.1 are affected, anything from 2.2.2 onward is not.

Remediation

Update to version 2.2.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Responsive Blocks 2.2.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-6703https://www.wordfence.com/threat-intel/vulnerabilities/id/187b072d-6314-4ac1-a924-b14324b2fd8dhttps://nvd.nist.gov/vuln/detail/CVE-2026-6703

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C