MaxiBlocks: 2200+ Patterns, 190 Pages, 14.2K Icons & 100 Styles <= 1.9.2 - Authenticated (Subscriber+) Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 1.9.3
- Affected Version
<= 1.9.2- CVSS
- 8.1High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2024-6885
At a glance
CVE-2024-6885 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the MaxiBlocks Builder WordPress plugin, affecting versions <= 1.9.2. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.9.3; sites on affected versions should update now. Disclosed July 2024, reported by Lucio Sá.
Vulnerability Overview
The MaxiBlocks: 2200+ Patterns, 190 Pages, 14.2K Icons & 100 Styles plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the maxi_remove_custom_image_size and maxi_add_custom_image_size functions in all versions up to, and including, 1.9.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
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 integrity, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in MaxiBlocks Builder <= 1.9.2 takes an account at Subscriber level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For MaxiBlocks Builder the fix is 1.9.3: builds <= 1.9.2 are affected, anything from 1.9.3 onward is not.
Remediation
Update to version 1.9.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MaxiBlocks Builder 1.9.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites
- 8.8CVE-2025-47601: MaxiBlocks Authenticated (Contributor+) Arbitrary
CVE-2025-47601 - 6.4CVE-2026-6378: Maxi Blocks <= 2.1.9 Stored Cross-Site Scripting
CVE-2026-6378 - 5.3CVE-2026-2028: Maxi Blocks Authenticated (Author+) Media File Deletion
CVE-2026-2028 - 4.3CVE-2025-58968: MaxiBlocks <= 2.1.3 Missing Authorization
CVE-2025-58968
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C