Vulnerability in WP Import – Ultimate CSV XML Importer for (WordPress plugin) (CVE-2025-10058)
Summary
Vulnerability in WP Import – Ultimate CSV XML Importer for (WordPress plugin) (CVE-2025-10058). Data can be tampered with by attackers.
Original description
The description as published by the source.
The WP Import – Ultimate CSV XML Importer for WordPress plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the upload_function() function in all versions up to, and including, 7.27. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-10058 has been found in WP Import – Ultimate CSV XML Importer for (WordPress plugin).
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WP Import – Ultimate CSV XML Importer for (WordPress plugin) CVE-2025-10058" on the vendor's site.
CVE-2025-10058 (WP Import – Ultimate CSV XML Importer for (WordPress plugin)) — CWE-73 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) exists in WP Import – Ultimate CSV XML Importer for (WordPress plugin).
Check the vendor advisory for the affected versions of WP Import – Ultimate CSV XML Importer for (WordPress plugin).
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WP Import – Ultimate CSV XML Importer for (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。