CVE-2025-11170
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 · uneditedThe WP移行専用プラグイン for CPI plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the Cpiwm_Import_Controller::import function in all versions up to, and including, 1.0.2. This makes it possible for unauthenticated attackers 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 confidenceThe WP移行専用プラグイン for CPI WordPress plugin is vulnerable to unauthenticated arbitrary file uploads due to missing file type validation in the Cpiwm_Import_Controller::import function. Attackers can upload malicious files directly to the server without authentication, potentially achieving remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the plugin is installedCheck WordPress plugin directory wp-content/plugins/ for a folder related to 'WP移行専用プラグイン' or 'CPI' migration plugin, or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if The plugin 'WP移行専用プラグイン for CPI' or similar CPI migration plugin appears in the plugin list
-
Determine the installed plugin versionClick on the plugin in WordPress admin to view its details, or open the main plugin PHP file and look for 'Version:' in the plugin header commentAffected if The version is below 1.0.3, or the version cannot be determined and the plugin is installed
-
Check for suspicious PHP files in web-accessible directoriesSearch wp-content/uploads/ and the WordPress root directory for .php files that were not intentionally uploaded, especially files with random names or ones created recentlyAffected if Unexpected PHP files are found in upload folders or WordPress root that do not belong to the site
-
Review web server access logs for import function requestsExamine Apache/nginx access logs for POST requests to endpoints containing 'import' or 'cpiwm' - typical paths may include /wp-admin/admin-ajax.php or custom endpointsAffected if Unexplained POST requests to import-related endpoints appear in logs, especially from unknown IP addresses
-
Check for newly created admin accounts or compromised user accountsIn WordPress admin, go to Users > All Users and review for unfamiliar administrators or users created recentlyAffected if New or unauthorized administrator accounts exist that were not created by known site administrators
If the WP移行専用プラグイン for CPI plugin is installed and its version is below 1.0.3 (or the version cannot be verified), the environment is likely affected by this vulnerability and may have unauthorized files uploaded.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to a patched version once available, or disable and remove the plugin if not essential. Consider implementing WAF rules to block suspicious file upload requests in the interim.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11170 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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