dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-3412

CRITICAL · 9.1 CVSS v3.1 Published 2024-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/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 WP STAGING WordPress Backup Plugin – Migration Backup Restore plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the wpstg_processing AJAX action in all versions up to, and including, 3.4.3. This makes it possible for authenticated attackers, with administrator-level access and above, 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 WP STAGING plugin fails to validate file types in the wpstg_processing AJAX action, allowing authenticated administrators to upload arbitrary files to the server. This arbitrary file upload capability can be leveraged to achieve remote code execution.

MitigationUpdate the WP STAGING plugin to version 3.4.4 or later which contains the file type validation fix. If an update is unavailable, disable the plugin immediately.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm WP STAGING plugin is installed
    Check your WordPress site's plugin directory for the WP STAGING plugin, or log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to verify WP STAGING is present
    Affected if WP STAGING plugin is not installed on the WordPress site
  2. Identify the installed WP STAGING version
    In the WordPress admin under Plugins > Installed Plugins, find WP STAGING and note the version number displayed. Alternatively, inspect the plugin's main PHP file header for the Version field
    Affected if The installed version is any version earlier than 3.4.4 (the vulnerable version range is not precisely defined but versions prior to the fix are affected)
  3. Verify the wpstg_processing AJAX action is accessible
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php?action=wpstg_processing is reachable. This requires an authenticated administrator session to test the vulnerable endpoint
    Affected if The AJAX endpoint responds and accepts file upload requests from authenticated administrators
  4. Confirm file upload functionality is enabled
    Review the WP STAGING plugin settings to determine if staging site creation or backup/restore features that leverage the file upload mechanism are active
    Affected if File upload capabilities in WP STAGING are enabled and accessible to administrator-level users

If WP STAGING is installed with a version earlier than 3.4.4 and the wpstg_processing AJAX action is accessible to administrators with file upload capabilities enabled, the environment is vulnerable to arbitrary file upload and potential remote code execution.

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 WP STAGING plugin to version 3.4.4 or later which contains the file type validation fix. If an update is unavailable, disable the plugin immediately.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version 3.4.4 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP STAGING plugin
  4. Check the current installed version
  5. If the installed version is 3.4.3 or lower, update the plugin to the latest available version from the WordPress plugin repository
  6. After updating, verify the new version number reflects the update
  7. Test that the wpstg_processing AJAX functionality works correctly for legitimate backup operations

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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