Plugins · export-user-data · data as of 2026-11-04
Is Export User Data safe? Known vulnerabilities and latest version
- Status
- Closed 2026-06-25
- Known issues on record
- 2
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate export-user-data && wp plugin delete export-user-data
Check your version
Known vulnerabilities
2 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. 2 record(s) do not state which versions are affected.
critical 9.8 CVE-2026-65552 · published 2026-08-06
PHP object injection in Export User Data (2.2.6 and older)
- Affected
- 2.2.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Subscriber PHP Object Injection in Export User Data <= 2.2.6 versions.
high 8.0 CVE-2026-12240 · published 2026-06-30
Arbitrary file deletion in Export User Data (2.2.6 and older)
- Affected
- 2.2.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Export User Data plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the unserialize function in all versions up to, and including, 2.2.6. 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). Successful exploitation requires an administrator to trigger a user data export while a subscriber-level (or higher) user has stored a crafted serialized XLSXWriter object payload as their display name.
Recent activity
- 2026-06-25 — closed on wordpress.org (Security Issue).
- 2026-08-06 — PHP object injection disclosed (CVE-2026-65552), fix version not stated.
- 2026-06-30 — Arbitrary file deletion disclosed (CVE-2026-12240), fix version not stated.
Get an email when Export User Data has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Export User Data (export-user-data) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: PHP object injection (1) · Arbitrary file deletion (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/export-user-data (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/export-user-data"><img src="https://laskyr.com/plugins/export-user-data/badge.svg" alt="Export User Data vulnerability status"></a>