CVE-2026-2028

Maxi Blocks <= 2.1.8 - Missing Authorization to Authenticated (Author+) Media File Deletion via 'old_media_src' Parameter

2026-04-23 14:43
Teerachai Somprasong

Strategic Overview

Status
Patched in 2.1.9
Affected Plugin
MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites
Affected Version
<= 2.1.8
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-2028
View all MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites vulnerabilities

At a glance

CVE-2026-2028 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the MaxiBlocks Builder WordPress plugin, affecting versions <= 2.1.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.9; sites on affected versions should update now. Disclosed April 2026, reported by Teerachai Somprasong.

Vulnerability Overview

The MaxiBlocks Builder plugin for WordPress is vulnerable to arbitrary media file deletion due to insufficient file ownership validation on the 'maxi_remove_custom_image_size' AJAX action in all versions up to, and including, 2.1.8. This makes it possible for authenticated attackers, with Author-level access and above, to delete arbitrary files in the wp-content/uploads directory, including files uploaded by other users and administrators.

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 privileges on the target site, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

MaxiBlocks Builder <= 2.1.8 carries this weakness at maxi_remove_custom_image_size, and reaching it takes an account at Author level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For MaxiBlocks Builder the fix is 2.1.9: builds <= 2.1.8 are affected, anything from 2.1.9 onward is not.

Remediation

Update to version 2.1.9, 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.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2028https://www.wordfence.com/threat-intel/vulnerabilities/id/f50c31df-56d0-4c34-a93c-56198fe91b36https://nvd.nist.gov/vuln/detail/CVE-2026-2028

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C