Is Responsive Blocks safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.3.0). As of 2026-11-04. 11 issues are on record for older versions; version 2.3.0 or newer fixes all of them that state a fix. Keep Responsive Blocks on the latest version (2.3.0) and remove it if you do not use it.

Which versions of Responsive Blocks are vulnerable?

Known issues on record (newest first): Content injection (older than 2.3.0, fixed in 2.3.0); Missing authorization check (2.0.9 to 2.2.1, fixed in 2.2.2); Security issue (2.2.0 and older, fixed in 2.2.1); Missing authorization check (2.2.0 and older, fixed in 2.2.1); Cross-site scripting (XSS) (2.0.6 and older, fixed in 2.0.7); Stored cross-site scripting (XSS) (2.0.5 and older, fixed in 2.0.6). The full list with sources is on this page.

What is the latest version of Responsive Blocks?

2.3.0, according to wordpress.org (last updated 2026-10-06). It has 3,000+ active installs.

What should I do if my Responsive Blocks is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update responsive-block-editor-addons). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · responsive-block-editor-addons · data as of 2026-11-04

Is Responsive Blocks safe? Known vulnerabilities and latest version

Latest version: 2.3.0
Last updated: 2026-10-06
Active installs: 3,000+
Known issues on record: 11
Unpatched in latest: 0
Tested up to WP: 6.9.11 · PHP 5.6+

50+ blocks to create rich sections in the Gutenberg editor. Use professional starter block patterns & templates to create websites within minutes. — by CyberChimps

What to do

Update to the latest version (2.3.0). Anything older than 2.3.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get responsive-block-editor-addons --field=version shows what you run; wp plugin update responsive-block-editor-addons updates it.

Check your version

Known vulnerabilities

11 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.4 CVE-2026-97315 · published 2026-10-14

Content injection in Responsive Blocks (older than 2.3.0)

Affected: older than 2.3.0
Fixed in: 2.3.0
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by WPScan

Details from the advisory

The Responsive Blocks WordPress plugin before 2.3.0 does not sanitise or escape some of the values submitted with its Form block before adding them to the HTML notification email sent to the site owner, allowing unauthenticated users to inject arbitrary HTML, such as phishing links, into that email.

NVD CVE-2026-97315 WPScan advisory

medium 4.3 CVE-2026-6703 · published 2026-04-21

Missing authorization check in Responsive Blocks (2.0.9 to 2.2.1)

Affected: 2.0.9 to 2.2.1
Fixed in: 2.2.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-6703 Wordfence advisory Code change (fix)Plugin source

medium 5.3 CVE-2026-6675 · published 2026-04-21

Security issue in Responsive Blocks (2.2.0 and older)

Affected: 2.2.0 and older
Fixed in: 2.2.1 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-6675 Wordfence advisory Plugin source

medium 5.3 CVE-2026-32543 · published 2026-03-13

Missing authorization check in Responsive Blocks (2.2.0 and older)

Affected: 2.2.0 and older
Fixed in: 2.2.1
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in CyberChimps Responsive Blocks responsive-block-editor-addons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Responsive Blocks: from n/a through <= 2.2.0.

NVD CVE-2026-32543 Patchstack advisory

medium 6.5 CVE-2025-53202 · published 2025-06-27

Cross-site scripting (XSS) in Responsive Blocks (2.0.6 and older)

Affected: 2.0.6 and older
Fixed in: 2.0.7
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CyberChimps Responsive Blocks responsive-block-editor-addons allows DOM-Based XSS.This issue affects Responsive Blocks: from n/a through <= 2.0.6.

NVD CVE-2025-53202 Patchstack advisory

medium 6.5 CVE-2025-49881 · published 2025-06-17

Stored cross-site scripting (XSS) in Responsive Blocks (2.0.5 and older)

Affected: 2.0.5 and older
Fixed in: 2.0.6
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CyberChimps Responsive Blocks responsive-block-editor-addons allows Stored XSS.This issue affects Responsive Blocks: from n/a through <= 2.0.5.

NVD CVE-2025-49881 Patchstack advisory

medium 6.5 CVE-2025-39578 · published 2025-04-16

Stored cross-site scripting (XSS) in Responsive Blocks (2.0.2 and older)

Affected: 2.0.2 and older
Fixed in: 2.0.3
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CyberChimps Responsive Blocks responsive-block-editor-addons allows Stored XSS.This issue affects Responsive Blocks: from n/a through <= 2.0.2.

NVD CVE-2025-39578 Patchstack advisory

medium 5.4 CVE-2025-22697 · published 2025-02-04

Reflected cross-site scripting (XSS) in Responsive Blocks (1.9.9 and older)

Affected: 1.9.9 and older
Fixed in: 2.0.0
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CyberChimps Responsive Blocks responsive-block-editor-addons allows Reflected XSS.This issue affects Responsive Blocks: from n/a through <= 1.9.9.

NVD CVE-2025-22697 Patchstack advisory

medium 5.4 CVE-2024-13732 · published 2025-01-30

Stored cross-site scripting (XSS) in Responsive Blocks (1.9.9 and older)

Affected: 1.9.9 and older
Fixed in: 2.0.0 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Responsive Blocks – WordPress Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘section_tag’ parameter in all versions up to, and including, 1.9.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2024-13732 Wordfence advisory Code change (fix)wordpress.org Plugin source

medium 5.4 CVE-2024-12268 · published 2024-12-24

Stored cross-site scripting (XSS) in Responsive Blocks (1.9.7 and older)

Affected: 1.9.7 and older
Fixed in: 1.9.8 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Responsive Blocks – WordPress Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'responsive-block-editor-addons/portfolio' block in all versions up to, and including, 1.9.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2024-12268 Wordfence advisory Code change (fix)

medium 5.4 CVE-2024-43335 · published 2024-08-18

Stored cross-site scripting (XSS) in Responsive Blocks (1.8.8 and older)

Affected: 1.8.8 and older
Fixed in: 1.8.9
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in CyberChimps Responsive Blocks – WordPress Gutenberg Blocks allows Stored XSS.This issue affects Responsive Blocks – WordPress Gutenberg Blocks: from n/a through 1.8.8.

NVD CVE-2024-43335 Patchstack advisory

Recent activity

2026-10-06 — latest release on wordpress.org (2.3.0).
2026-10-14 — Content injection disclosed (CVE-2026-97315), fixed in 2.3.0.
2026-04-21 — Missing authorization check disclosed (CVE-2026-6703), fixed in 2.2.2.
2026-04-21 — Security issue disclosed (CVE-2026-6675), fixed in 2.2.1.

Free. We check the CVE feeds every day and email you only when a new issue for Responsive Blocks (responsive-block-editor-addons) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (7) · Missing authorization (2) · Content injection (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/responsive-block-editor-addons (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/responsive-block-editor-addons"><img src="https://laskyr.com/plugins/responsive-block-editor-addons/badge.svg" alt="Responsive Blocks vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Responsive Blocks safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.3.0)

What to do

Check your version

Known vulnerabilities

Content injection in Responsive Blocks (older than 2.3.0)

Missing authorization check in Responsive Blocks (2.0.9 to 2.2.1)

Security issue in Responsive Blocks (2.2.0 and older)

Missing authorization check in Responsive Blocks (2.2.0 and older)

Cross-site scripting (XSS) in Responsive Blocks (2.0.6 and older)

Stored cross-site scripting (XSS) in Responsive Blocks (2.0.5 and older)

Stored cross-site scripting (XSS) in Responsive Blocks (2.0.2 and older)

Reflected cross-site scripting (XSS) in Responsive Blocks (1.9.9 and older)

Stored cross-site scripting (XSS) in Responsive Blocks (1.9.9 and older)

Stored cross-site scripting (XSS) in Responsive Blocks (1.9.7 and older)

Stored cross-site scripting (XSS) in Responsive Blocks (1.8.8 and older)

Recent activity

Get an email when Responsive Blocks has a new vulnerability

Browse vulnerabilities

Where this data comes from