dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-37424

CRITICAL · 9.9 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Unrestricted Upload of File with Dangerous Type vulnerability in Automattic Newspack Blocks allows Upload a Web Shell to a Web Server.This issue affects Newspack Blocks: from n/a through 3.0.8.

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

Automattic Newspack Blocks plugin versions through 3.0.8 contain an unrestricted file upload vulnerability that allows authenticated attackers to upload files with dangerous types (such as PHP scripts) to the web server, potentially leading to remote code execution via web shell deployment.

MitigationUpgrade Newspack Blocks to the latest version and implement strict allowlist-based file type validation with content-type verification to prevent upload of executable files.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 if Newspack Blocks plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/newspack-blocks/) or view installed plugins in WP Admin under Plugins > Installed Plugins
    Affected if Newspack Blocks appears in the list of installed plugins
  2. Determine installed version of Newspack Blocks
    Locate the main plugin file (usually newspack-blocks.php) and check the version header in the file comments, or check the plugin's readme.txt file
    Affected if Version is 3.0.8 or earlier (any version through 3.0.8)
  3. Confirm authenticated user access to file upload feature
    Review user roles and capabilities in WordPress (Users > All Users) to determine if any non-administrator accounts exist that could access the plugin's upload functionality
    Affected if Any authenticated user role (subscriber, contributor, author, editor) can access the site and the plugin's upload endpoint
  4. Inspect file upload configuration
    If you have access to the server, examine the plugin's PHP files related to file upload handling in wp-content/plugins/newspack-blocks/ and check for file type validation logic
    Affected if No server-side file type validation is enforced, or the validation allows executable extensions like .php, .phtml, .phar
  5. Check uploaded files directory
    Review the wp-content/uploads/ directory and any custom upload paths configured in the plugin for any recently uploaded files with dangerous extensions
    Affected if Files with .php, .phtml, or other executable extensions exist in upload directories

Your environment is affected if the Newspack Blocks plugin is installed with version 3.0.8 or earlier and authenticated users can access the file upload functionality.

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

Upgrade Newspack Blocks to the latest version and implement strict allowlist-based file type validation with content-type verification to prevent upload of executable files.

Recommended fix Moderate confidence

Newspack Blocks version higher than 3.0.8 (likely 3.0.9 or later)

  1. 1. Identify the currently installed version of the Newspack Blocks plugin in your WordPress installation
  2. 2. If the installed version is 3.0.8 or earlier, plan for an upgrade to a fixed release
  3. 3. Before upgrading, perform a full backup of the WordPress site including database and files
  4. 4. Test the upgrade in a staging environment first if possible
  5. 5. Upgrade the Newspack Blocks plugin to the latest available version (which should be higher than 3.0.8)
  6. 6. Verify the upgrade was successful by checking the plugin version
  7. 7. Test that the plugin functionality remains working as expected
  8. 8. Monitor the site for any anomalies
Caveat Review the plugin changelog for any breaking changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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