MaxiBlocks <= 2.1.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Options Update
Strategic Overview
- Status
- Patched in 2.1.1
- Affected Version
<= 2.1.0- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-47601
At a glance
CVE-2025-47601 is a high-severity Missing Authorization vulnerability in the MaxiBlocks Builder WordPress plugin, affecting versions <= 2.1.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.1.1; sites on affected versions should update now. Disclosed May 2025, reported by Cút lộn xào me.
Vulnerability Overview
The MaxiBlocks: 2300+ Patterns, 280+ Pages, 14.3K Icons & 100 Styles plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on a function in all versions up to, and including, 2.1.0. This makes it possible for authenticated attackers, with Contributor-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in MaxiBlocks Builder <= 2.1.0 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 MaxiBlocks Builder the fix is 2.1.1: builds <= 2.1.0 are affected, anything from 2.1.1 onward is not.
Remediation
Update to version 2.1.1, 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: MaxiBlocks Builder 2.1.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C