Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-2028Published · Updated

Action summary

Affected: ≤2.1.8Update to 2.1.9 or newer

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites maxi-blocks

  1. Affected≤ 2.1.8
  2. Patched in2.1.9

Update to 2.1.9 or newer.

You are affected if you run ≤ 2.1.8. Version 2.1.9 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.1.9, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Teerachai Somprasong.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites

All 5
More vulnerabilities in MaxiBlocks Builder | 17,000+ Design Assets, Patterns, Icons & Starter Sites
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Author+) Stored Cross-Site Scripting via Style Card REST API
≤2.1.9Update to 2.1.10
CVE-2026-6378
Medium4.3Missing Authorization
≤2.1.3Update to 2.1.4
CVE-2025-58968
High8.8Missing Authorization to Authenticated (Contributor+) Arbitrary Options Update
≤2.1.0Update to 2.1.1
CVE-2025-47601
High8.1Authenticated (Subscriber+) Arbitrary File Deletion
≤1.9.2Update to 1.9.3
CVE-2024-6885

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?