dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-3455

HIGH · 8.8 CVSS v3.1 Published 2025-05-09
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 1 Click WordPress Migration Plugin – 100% FREE for a limited time plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'start_restore' function in all versions up to, and including, 2.2. This makes it possible for authenticated attackers, with Subscriber-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 1 Click WordPress Migration Plugin has a missing capability check on the 'start_restore' function in versions up to 2.2, allowing authenticated users with Subscriber-level permissions to trigger arbitrary file uploads to the server, potentially leading to remote code execution.

MitigationUpdate the plugin to the latest version beyond 2.2 when available, or disable the plugin until a patch can be applied. Restrict user registration to prevent unauthorized subscriber accounts.

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. Confirm the 1 Click WordPress Migration plugin is installed
    Check the WordPress plugins directory for the plugin folder, or list installed plugins via wp-admin > Plugins. The plugin typically appears as '1 Click Migration' or '1 Click WP Migration'.
    Affected if The plugin is present on the WordPress site
  2. Identify the installed plugin version
    Access the plugin details in wp-admin > Plugins > 1 Click Migration, or inspect the main plugin PHP file (usually 1-click-wp-migration/storage/include/class-1-click-wp-migration-storage.php or similar) to find the version defined in the plugin header comment.
    Affected if The version is lower than 2.3.0 or the version cannot be determined (treat as vulnerable)
  3. Verify if subscriber-level user accounts exist
    Navigate to wp-admin > Users and check for any users assigned the 'Subscriber' role. Alternatively, query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'.
    Affected if At least one user with Subscriber role exists in the WordPress installation
  4. Confirm the REST endpoint or AJAX action is exposed
    Inspect the plugin code for registered REST routes (wp-json/1clickwpmigration/v1/ or similar) or AJAX actions (wp_ajax_start_restore or similar). Check if these endpoints are accessible without capability verification by reviewing the plugin source code for 'add_action' or 'register_rest_route' calls related to 'start_restore'.
    Affected if The start_restore function is exposed without a capability check (any authenticated user can trigger it)

The site is affected if the 1 Click WordPress Migration plugin version is below 2.3 and at least one Subscriber-level user account exists, allowing that user to trigger arbitrary file uploads via the unprotected start_restore function.

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 plugin to the latest version beyond 2.2 when available, or disable the plugin until a patch can be applied. Restrict user registration to prevent unauthorized subscriber accounts.

Recommended fix Moderate confidence

Plugin version 2.3 or later (update to latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the '1 Click WordPress Migration Plugin'
  4. Check if an update is available and update to the latest version
  5. Alternatively, delete the current plugin and reinstall the latest version from the WordPress plugin repository

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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