Is Import WP safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.15.2). As of 2026-11-04. 5 issues are on record for older versions; version 2.14.23 or newer fixes all of them that state a fix. Keep Import WP on the latest version (2.15.2) and remove it if you do not use it.

Which versions of Import WP are vulnerable?

Known issues on record (newest first): Information disclosure (older than 2.14.23, fixed in 2.14.23); Information disclosure (2.14.17 and older, fixed in 2.14.18); Path traversal / file read (2.14.16 and older, fixed in 2.14.17); Server-side request forgery (SSRF) (older than 2.13.1, fixed in 2.13.1); Remote code execution (older than 2.4.6, fixed in 2.4.6). The full list with sources is on this page.

What is the latest version of Import WP?

2.15.2, according to wordpress.org (last updated 2026-10-08). It has 4,000+ active installs.

What should I do if my Import WP is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update jc-importer). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · jc-importer · data as of 2026-11-04

Is Import WP safe? Known vulnerabilities and latest version

Latest version: 2.15.2
Last updated: 2026-10-08
Active installs: 4,000+
Known issues on record: 5
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 5.6+

Import and export WordPress posts, pages, users and media from any CSV or XML file, URL, FTP or Google Sheets — with visual field mapping. — by jcollings

What to do

Update to the latest version (2.15.2). Anything older than 2.14.23 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get jc-importer --field=version shows what you run; wp plugin update jc-importer updates it.

Check your version

Known vulnerabilities

5 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.5 CVE-2026-14925 · published 2026-08-12

Information disclosure in Import WP (older than 2.14.23)

Affected: older than 2.14.23
Fixed in: 2.14.23
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

The Import WP WordPress plugin before 2.14.23 does not perform any authorization check on one of its export-file download handlers, allowing unauthenticated attackers to download export files generated by administrators, which may contain user personal data such as email addresses, login names and roles. Exploitation requires an unconsumed export to already exist and a low-entropy, time-based download key to be obtained.

NVD CVE-2026-14925 WPScan advisory

medium 5.3 CVE-2025-12894 · published 2025-11-21

Information disclosure in Import WP (2.14.17 and older)

Affected: 2.14.17 and older
Fixed in: 2.14.18 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Import WP – Export and Import CSV and XML files to WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.14.17 via the import/export functionality and a lack of .htaccess protection. This makes it possible for unauthenticated attackers to extract sensitive data from exports stored in /exportwp and import data stored in /importwp.

NVD CVE-2025-12894 Wordfence advisory Code change (fix)

medium 4.9 CVE-2025-12137 · published 2025-11-01

Path traversal / file read in Import WP (2.14.16 and older)

Affected: 2.14.16 and older
Fixed in: 2.14.17 *
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Import WP – Export and Import CSV and XML files to WordPress plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 2.14.16. This is due to the plugin's REST API endpoint accepting arbitrary absolute file paths without proper validation in the 'attach_file()' function when handling 'file_local' actions. This makes it possible for authenticated attackers, with administrator-level access and above, to read arbitrary files on the server's filesystem, including sensitive configuration files and system files via the 'local_url' parameter.

NVD CVE-2025-12137 Wordfence advisory Code change (fix)cwe.mitre.org github.com owasp.org Plugin source

medium 6.1 CVE-2023-7253 · published 2024-04-24

Server-side request forgery (SSRF) in Import WP (older than 2.13.1)

Affected: older than 2.13.1
Fixed in: 2.13.1
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

The Import WP WordPress plugin before 2.13.1 does not prevent users with the administrator role from pinging conducting SSRF attacks, which may be a problem in multisite configurations.

NVD CVE-2023-7253 WPScan advisory

high 7.2 CVE-2022-1273 · published 2022-05-02

Remote code execution in Import WP (older than 2.4.6)

Affected: older than 2.4.6
Fixed in: 2.4.6
Access needed (per CVSS): Needs an admin-level account
Range from: advisory text · score by NVD

Details from the advisory

The Import WP WordPress plugin before 2.4.6 does not validate the imported file in some cases, allowing high privilege users such as admin to upload arbitrary files (such as PHP), leading to RCE

NVD CVE-2022-1273 WPScan advisory

Recent activity

2026-10-08 — latest release on wordpress.org (2.15.2).
2026-08-12 — Information disclosure disclosed (CVE-2026-14925), fixed in 2.14.23.
2025-11-21 — Information disclosure disclosed (CVE-2025-12894), fixed in 2.14.18.
2025-11-01 — Path traversal / file read disclosed (CVE-2025-12137), fixed in 2.14.17.

Free. We check the CVE feeds every day and email you only when a new issue for Import WP (jc-importer) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Sensitive data exposure (2) · Path traversal and file read (1) · Server-side request forgery (SSRF) (1) · Remote code execution (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/jc-importer (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/jc-importer"><img src="https://laskyr.com/plugins/jc-importer/badge.svg" alt="Import WP vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Import WP safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.15.2)

What to do

Check your version

Known vulnerabilities

Information disclosure in Import WP (older than 2.14.23)

Information disclosure in Import WP (2.14.17 and older)

Path traversal / file read in Import WP (2.14.16 and older)

Server-side request forgery (SSRF) in Import WP (older than 2.13.1)

Remote code execution in Import WP (older than 2.4.6)

Recent activity

Get an email when Import WP has a new vulnerability

Browse vulnerabilities

Where this data comes from