CVE-2026-86583: Import and export users and customers <= 2.4.17 - Authenticated (Subscriber+) Privilege Escalation via CSV Escape-Character Mismatch in Export/Import Round Trip via display_name and nickname Profile Fields

Published Sep 23, 2026
·
Updated

The Import and export users and customers plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.4.17 via the plugin's own export and re-import workflow. The vulnerability exists because the exporter writes CSV cells using fputcsv() with a NUL byte (\0) as the escape character, while the importer parses the same file using SplFileObject::fgetcsv() with only a single delimiter argument, causing PHP's default backslash escape character to be applied instead; because the export column layout places displayname immediately before the role column and nickname immediately after, an attacker can store crafted values in those two profile fields — saved by WordPress core via the standard profile page — such that the escape mismatch causes the parser to merge the displayname cell into the role field and rebalance the column count via nickname, yielding administrator as the parsed role for their own row when it reaches the importuser function's addrole function. This makes it possible for authenticated attackers with Subscriber-level access or above to escalate their privileges to Administrator. Exploitation requires a site administrator to trigger the plugin's documented export re-import migration with both "Update existing users" and "Update roles for existing users" set to "yes".

Affected Software

1 affected component
WebToffee Import and Export WordPress Users and WooCommerce Customers<=2.4.17

Event History

Sep 23, 2026
CVE Published
via MITRE·09:27 PM
Data Sourced
via MITRE·09:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which users can initiate the privilege-escalation chain?

Any authenticated user with Subscriber-level access or higher can prepare the required crafted profile-field values. The affected fields are display_name and nickname.

2

Does exploitation require administrator involvement?

Yes. The attack depends on the plugin's export and re-import workflow, and exploitation requires a site administrator to trigger that workflow. The attacker’s crafted profile data is preserved through the standard WordPress profile page.

3

What versions should be treated as affected?

All versions through 2.4.17, including 2.4.17, are affected according to the available information.

4

What can be done while patching is not possible?

Avoid exporting and then re-importing user data that may contain values controlled by lower-privileged users, particularly display_name and nickname fields. Restrict access to the export/import workflow to trusted administrators.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203