Responsive Blocks · Security record
Is Responsive Blocks safe?
No known vulnerability affects the current version (2.3.0). 11 issues were found in earlier versions and fixed, the latest disclosed on Apr 20, 2026.
Checked 5 days ago against the WPVulnerability database, for version 2.3.0.
How it’s looked after
- Last release
- Oct 6, 2026 (1 month ago)
- Releases in the last year
- 16
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Active installs
- 3K+
11 known vulnerabilities
- 11 medium
None affects the current version.
Disclosed each year
- 20242
- 20255
- 20264
Every known vulnerability in Responsive Blocks
Newest first, with any that affect the current version at the top.
Fixed in 2.3.0 · CVE-2026-97315 · Apr 20, 2026 · Wordfence
Fixed in 2.2.1 · CVE-2026-6675 · Apr 20, 2026 · Wordfence
Fixed in 2.2.2 · CVE-2026-6703 · Apr 20, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 2.2.1 · CVE-2026-32543 · Mar 11, 2026 · Wordfence
Fixed in 2.0.7 · CVE-2025-53202 · Jun 27, 2025 · Wordfence
Fixed in 2.0.6 · CVE-2025-49881 · Jun 12, 2025 · Wordfence
Fixed in 2.0.3 · CVE-2025-39578 · Apr 16, 2025 · Wordfence
Fixed in 2.0.0 · CVE-2025-22697 · Jan 31, 2025 · Wordfence
Fixed in 2.0.0 · CVE-2024-13732 · Jan 29, 2025 · Wordfence
Fixed in 1.9.8 · CVE-2024-12268 · Dec 23, 2024 · Wordfence
Fixed in 1.8.9 · CVE-2024-43335 · Aug 16, 2024 · Wordfence
Questions about Responsive Blocks’s security
Is Responsive Blocks safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Responsive Blocks updated: most attacks target sites that haven’t updated.
Does Responsive Blocks have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 11 older issues, fixed in earlier versions, so keep Responsive Blocks up to date.
Is Responsive Blocks still maintained?
Yes. Its last release was 1 month ago. No support threads were opened in the last two months.
Is Responsive Blocks compatible with the latest WordPress?
Responsive Blocks’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.