dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-6315

HIGH · 8.8 CVSS v3.1 Published 2024-08-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Blox Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'handleUploadFile' function in all versions up to, and including, 1.0.65. This makes it possible for authenticated attackers, with contributor-level and above permissions, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Blox Page Builder WordPress plugin has an arbitrary file upload vulnerability in the handleUploadFile function. The function lacks proper file type validation, allowing authenticated users with contributor-level or higher permissions to upload any file type to the server, which can be leveraged for remote code execution.

MitigationUpdate the Blox Page Builder plugin to version 1.0.66 or later, which includes proper file type validation in the handleUploadFile function. Until updated, restrict file upload capabilities or disable the plugin.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Blox Page Builder plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a blox-page-builder folder
    Affected if The Blox Page Builder plugin folder exists in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for the Blox Page Builder entry to view the version number, or check the plugin's main PHP file for a Version header comment
    Affected if The installed version is lower than 1.0.66 (the version that contains the fix)
  3. Confirm contributor-level or higher users exist
    Navigate to Users > All Users in WordPress admin and identify if any accounts have the Contributor, Author, Editor, or Administrator role
    Affected if At least one user with Contributor-level permissions or higher exists in the WordPress site
  4. Check if file upload is enabled for contributor roles
    Review the user role capabilities by examining the role definitions in WordPress or using a role management plugin; specifically check if the upload_files capability is granted to Contributor role
    Affected if The upload_files capability is assigned to Contributor, Author, or Editor roles
  5. Inspect the handleUploadFile function for validation
    Examine the Blox Page Builder plugin files (typically in the includes or classes directory) and locate the handleUploadFile function; check if it contains proper file type validation (such as checking file extensions or MIME types before allowing uploads)
    Affected if The handleUploadFile function lacks file type validation checks (e.g., no extension allowlist, no MIME type verification)

A user is affected if the Blox Page Builder plugin is installed with a version below 1.0.66, the site has users with contributor-level permissions, and the plugin's handleUploadFile function does not perform proper file type validation.

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 Blox Page Builder plugin to version 1.0.66 or later, which includes proper file type validation in the handleUploadFile function. Until updated, restrict file upload capabilities or disable the plugin.

Recommended fix Moderate confidence

1.0.66 or later

  1. 1. Update the Blox Page Builder plugin to version 1.0.66 or later, as versions up to and including 1.0.65 are vulnerable to arbitrary file uploads.
  2. 2. After updating, verify the plugin is functioning correctly on the site.
  3. 3. Review recent user accounts with contributor-level or higher permissions to ensure no unauthorized changes were made.
  4. 4. Monitor server logs for any suspicious file upload attempts that may have occurred before 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6315 — 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-6315 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