dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-6885

HIGH · 8.1 CVSS v3.1 Published 2024-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MaxiBlocks WordPress plugin (versions up to 1.9.2) contains arbitrary file deletion vulnerability in the maxi_remove_custom_image_size and maxi_add_custom_image_size functions due to insufficient file path validation. Authenticated attackers with Subscriber-level access can delete arbitrary files on the server, potentially leading to remote code execution by deleting critical files like wp-config.php.

MitigationUpdate the MaxiBlocks plugin to version 1.9.3 or later. Until then, revoke Subscriber-level user capabilities or temporarily disable the plugin to prevent exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify MaxiBlocks plugin version
    Go to WordPress dashboard > Plugins > Installed Plugins, locate MaxiBlocks, and check the version number displayed. Alternatively, inspect the plugin's main PHP file header or check wp_options table for the plugin version entry.
    Affected if The installed version is 1.9.2 or lower (versions up to and including 1.9.2 are vulnerable).
  2. Confirm MaxiBlocks plugin is active
    In WordPress admin, check the Plugins page to see if MaxiBlocks shows as 'Active'. Also verify via wp_options table where option_name = 'active_plugins' and option_value contains 'maxiblocks'.
    Affected if The plugin is active and running on a vulnerable version (inactive plugins on vulnerable versions are not exploitable).
  3. Check for Subscriber-level user accounts
    Navigate to WordPress dashboard > Users. Review all user accounts and identify any with the Subscriber role. Also query the wp_usermeta table: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%subscriber%'.
    Affected if Any active Subscriber-level user accounts exist in the WordPress installation.
  4. Verify the maxi_remove_custom_image_size and maxi_add_custom_image_size functions are accessible
    Inspect the MaxiBlocks plugin PHP files (typically in /wp-content/plugins/maxi-blocks/) for the maxi_remove_custom_image_size and maxi_add_custom_image_size functions. Confirm they are hooked to WordPress AJAX actions (wp_ajax_maxi_remove_custom_image_size and wp_ajax_maxi_add_custom_image_size) without capability checks requiring admin-level access.
    Affected if The vulnerable AJAX endpoints are registered without capability checks, allowing Subscriber-level access.

Your environment is affected if MaxiBlocks plugin versions 1.9.2 or lower are active, the vulnerable AJAX functions are exposed without admin-only capability checks, and any Subscriber-level user accounts exist in WordPress.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the MaxiBlocks plugin to version 1.9.3 or later. Until then, revoke Subscriber-level user capabilities or temporarily disable the plugin to prevent exploitation.

Recommended fix Moderate confidence

1.9.3 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the MaxiBlocks plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Verify the plugin has been updated to version 1.9.3 or higher
  6. Test that the website functionality remains intact after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6885 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data