CVE-2026-32543
Missing Authorization in CyberChimps Responsive Blocks
Publication date: 2026-03-13
Last updated on: 2026-03-13
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cyberchimps | responsive_blocks | to 2.2.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-32543 is a broken access control vulnerability in the WordPress Responsive Blocks Plugin versions up to and including 2.2.0.
This issue arises from missing authorization, authentication, or nonce token checks in certain functions, allowing unauthenticated users to perform actions reserved for higher-privileged users.
The vulnerability has a CVSS score of 5.3, indicating a low severity impact and is classified under OWASP Top 10 category A1: Broken Access Control.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated users to perform actions that should be restricted to higher-privileged users due to missing authorization checks.
Exploiting this issue could lead to unauthorized modifications or control within the affected plugin, potentially compromising the integrity of the website using it.
However, the impact is considered low severity with a CVSS score of 5.3.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-32543 vulnerability, you should update the WordPress Responsive Blocks Plugin to version 2.2.1 or later, as this version contains the patch that resolves the broken access control issue.
Additionally, enabling auto-update options for the affected plugin can provide rapid protection against this vulnerability.