dbcve.org
1 Click MigrationWordPress extension · 1clickmigration

CVE-2024-13609

MEDIUM · 5.9 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 2.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Sensitive Information Exposure in all versions up to, and including, 2.2 via the class-ocm-backup.php. This makes it possible for unauthenticated attackers to extract sensitive data including usernames and their respective password hashes during a short window of time in which the backup is in process.

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 · moderate confidence

The 1 Click WordPress Migration Plugin (versions up to 2.2) exposes sensitive data including WordPress usernames and their password hashes through the class-ocm-backup.php file. Unauthenticated attackers can extract this data during the brief window when a backup operation is in progress, due to insufficient access controls on backup files.

MitigationUpdate the plugin to the latest version once available. Until then, disable the plugin or ensure backups are not accessible to unauthenticated users by restricting filesystem access and removing backup files immediately after creation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
1 Click MigrationWordPress extension
Affected:<= 2.1

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

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

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. Check plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find '1clickmigration 1 Click Migration' or check the plugin header in its main PHP file for the Version constant
    Affected if The installed version is 2.1 or lower
  2. Verify vulnerable file exists
    Check if the file class-ocm-backup.php exists in the plugin directory at /wp-content/plugins/1clickmigration/ or similar path
    Affected if The file class-ocm-backup.php is present in the plugin directory
  3. Inspect backup directory permissions
    Check the wp-content directory for any newly created backup folders or files, and verify their file permissions using 'ls -la' or file manager
    Affected if Backup files are stored in a location accessible via web (readable by unauthenticated users)
  4. Test unauthenticated access to backup files
    Attempt to access a known or suspected backup file URL directly from a browser while not logged in, or check .htaccess / web server config for the backup directory
    Affected if Backup files can be downloaded by unauthenticated (not logged-in) users

A user is affected if the plugin version is 2.1 or lower AND backup files are accessible to unauthenticated users via the web.

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
Upgrade available Upgrade to a release after 2.1
Interim mitigation

Update the plugin to the latest version once available. Until then, disable the plugin or ensure backups are not accessible to unauthenticated users by restricting filesystem access and removing backup files immediately after creation.

Recommended fix Moderate confidence

Version 2.3 or later (upgrade to the latest available version of the 1 Click Migration plugin)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the '1 Click WordPress Migration Plugin' (1 Click Migration)
  4. Check if the currently installed version is 2.2 or earlier
  5. If vulnerable, click 'Update Now' to install the latest version, or manually download the updated plugin from the WordPress plugin repository

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

Fix this in 1 Click Migration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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