Responsive Block Control · Security record
Is Responsive Block Control safe?
No known vulnerability affects the current version (1.3.2). 1 issue was found in earlier versions and fixed, the latest disclosed on Dec 31, 2025.
Checked 4 days ago against the WPVulnerability database, for version 1.3.2.
How it’s looked after
- Last release
- Feb 21, 2026 (8 months ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Active installs
- 1K+
1 known vulnerability
- 1 not rated
None affects the current version.
Every known vulnerability in Responsive Block Control
Newest first, with any that affect the current version at the top.
Fixed in 1.3.1 · CVE-2025-62135 · Dec 31, 2025 · Wordfence
Questions about Responsive Block Control’s security
Is Responsive Block Control safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Responsive Block Control updated: most attacks target sites that haven’t updated.
Does Responsive Block Control have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Responsive Block Control up to date.
Is Responsive Block Control still maintained?
Its last release was 8 months ago. No support threads were opened in the last two months.
Is Responsive Block Control compatible with the latest WordPress?
Responsive Block Control’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.