Import and export users and customers

By Javier Carazo

★ 4.7/5 (259 ratings)70,000+ active installationsVersion 3.1.2

Bulk import and export WordPress users and WooCommerce customers from CSV, including roles, passwords and any custom meta.

Description

Try it on a free demo site: https://demo.tastewp.com/import-users-from-csv-with-meta

Import, export and migrate WordPress users and WooCommerce customers with a CSV file. A step by step assistant matches the columns of any file with WordPress and WooCommerce fields, shows you a preview of what will happen and imports thousands of users in batches, keeping their roles, passwords and custom fields.

✅ Tested with WordPress 7.1 and WooCommerce 11.3

✅ More than 70,000 active installations

✅ Free, with optional premium add-ons for special needs

🆕 New in 3.1

  • Export WooCommerce guest customers: the customers who bought without creating an account, with the billing and shipping details of their last order. Import the file later to create an account for each of them
  • Transform values while importing: replace a text (“United States” → “US”), add a prefix to phone numbers, change upper or lower case or fill empty cells, without editing the file
  • Add a field with the same value for every user, for data that is not in the file
  • Choose the columns of the export by checking them, drag them to change their order and rename them
  • Export specific users, searching them by email, username or name, and sort or limit the export
  • Export to Excel (XLSX), OpenDocument (ODS) or XML with the File Formats addon, also from the shortcode and the recurring exports
  • History of the last 100 imports and exports, with who made them, the file and the result

📥 Import users and customers

  • Any column names, any order. Columns like “E-mail”, “Correo electrónico”, “Prénom” or “Telefon” are recognised automatically in six languages, and the email column is detected by its content
  • Preview before importing: how many users will be created, updated or skipped, every row with an error and why, and a warning before any user is deleted. Nothing is saved until you start the import
  • Download the rows with errors as a CSV, fix them and import them again
  • Update existing users matched by ID, username or email, or skip them
  • Keep passwords when you migrate from another WordPress site, or generate new ones
  • Roles: one or several roles per user from a column of the file, or a default role
  • Welcome email with a customizable template, wildcards and a test button
  • Large files are imported in batches, so they do not time out
  • Files saved from Excel just work: the encoding (UTF-8 or Windows-1252) and the delimiter are detected for you
  • Templates: download a CSV with example data for users or WooCommerce customers
  • From your computer, a URL, Google Sheets or a file on the server
  • Import from the front-end with the [import-users] shortcode

📤 Export users and customers

  • Filter by role, registration date or specific users
  • Choose, order and rename the columns, or export all of them, custom fields included
  • Include WooCommerce guest customers
  • Export password hashes so users keep their passwords in another site
  • Sort the users and split big exports into several files
  • Export from the front-end with the [export-users] shortcode

⏱️ Automation

  • Recurring import from a file or a URL every hour, day or week, to keep your users in sync with a CRM, an ERP or any external list
  • History of every import and export, and a log of each recurring run
  • Hooks to extend everything: list of actions and filters

🔌 Works with your plugins

  • WooCommerce: billing and shipping fields, and guest customers
  • WooCommerce Subscriptions: create subscriptions while users are imported
  • WooCommerce Memberships and WooCommerce Membership by RightPress: memberships
  • Paid Memberships Pro (including version 3), Indeed Ultimate Membership Pro, Paid Member Subscriptions and WP Members: membership levels
  • BuddyPress: avatars, fields, groups and roles
  • Advanced Custom Fields: your own fields
  • WPML: translated front-end pages and emails (documentation)
  • Groups, Users Group, WP Users Group and WP Private Content Plus: groups
  • New User Approve: approve imported users or leave them pending
  • Clean Login: the login link of the welcome email takes your users to its login page
  • WP LMS Course: enroll users in courses
  • Allow Multiple Accounts: same rules while importing

💬 What users say

“The final import of all 900+ users was quick and precise. Everything smooth like oil.”
— Paolo Beccari

“I imported 31,000 users successfully, thanks to this plugin.”
— tbhpshop

“I needed to import users, send them login details, and add them to specific Paid Memberships Pro membership levels, all of which it did flawlessly.”
— David Robinson

“It even managed to import the custom roles that I created using the Members plugin.”
— Arischvaran Puvanesvaran

“I’ve used this for years, importing classlists and updating classlists each term with my courses.”
— wpnovice2

“The next morning, I had my fix in a new version. Amazing, personalized support.”
— pierre1wp

Read all the reviews

⭐ Premium add-ons

  • Allow No Email: import users who do not have an email address
  • File Formats: import XLSX, XLS and ODS spreadsheets and XML files directly, without converting them to CSV, and export to XLSX, ODS and XML
  • Recurring Import: unlimited scheduled import tasks, each with its own file, period, role and notification email, and the columns of each file mapped like in the import assistant
  • Recurring Export: unlimited scheduled export tasks, each saved to a folder of your server or sent by FTP, with its own filters, sorting and columns, WooCommerce guest customers and the XLSX, ODS and XML formats of the File Formats add-on
  • Dokan: import Dokan marketplace vendors
  • LearnDash: move LearnDash students between sites with their groups, courses, lessons and topics completed, quiz results and completion dates

🧭 How it works

Go to Tools > Import and export users and customers and follow the five steps:

  1. File: choose a CSV from your computer, a URL, Google Sheets or a file in your uploads folder
  2. Columns: check how each column will be imported, and transform values if you need to
  3. Options: default role, existing users and welcome email
  4. Preview: see what will happen and fix the rows with errors
  5. Import: the users are imported in batches, and the result is saved in the history

🛟 Need help?

  • Read the questions below and the Documentation tab of the plugin
  • Ask in the support forum
  • Premium support, migrations and custom development: contacto@codection.com

More plugins by Codection

Installation

  1. Install Import and export users and customers from Plugins > Add New, or upload the ZIP file in Plugins > Add New > Upload Plugin
  2. Activate it
  3. Go to Tools > Import and export users and customers

FAQ

What file formats can I import?

CSV files, in UTF-8 or in the Windows-1252 encoding used by Excel, with any delimiter (comma, semicolon, tab…). The encoding and the delimiter are detected automatically. To import XLSX, XLS or ODS spreadsheets or XML files directly, use the File Formats add-on.

Can I export to Excel?

The export creates a CSV file that Excel, LibreOffice and Google Sheets open directly. With the File Formats add-on you can also choose Excel (XLSX), OpenDocument (ODS) or XML in the “File format” option of the export, in the shortcode ([export-users format="xlsx"]) and in the recurring exports.

Do my columns need special names?

No. In the second step of the assistant you match each column with a WordPress field, a WooCommerce field or a custom field, and most columns are recognised automatically. Columns you do not need can be ignored. If you use the classic screen, the first two columns must be the username and the email.

Can I import WooCommerce customers?

Yes. Use columns for the billing and shipping fields (billing_first_name, billing_phone, shipping_address_1…) or match your own columns with them in the assistant. You can download a WooCommerce template with example data from the first step.

Can I export WooCommerce guest customers?

Yes, since version 3.1. Check “WooCommerce guest customers” in the Export tab: you get one row per billing email with the details of the last order. Emails that already belong to a registered user are skipped. If you import that file, an account is created for each guest with the email as username.

Can I migrate users from another WordPress site and keep their passwords?

Yes. Export the users with “Export password hashes” checked, and import the file in the new site matching the user_pass column as “Password hash (from another WordPress)”. Users keep the password they already had.

What happens with users who already exist?

Users are matched by ID, username or email. In the third step you choose whether to update them or skip them. Their passwords, roles and emails only change if you allow it in More options.

How are passwords managed?

If the file has no password column, new users get a random password, which they can receive in the welcome email or change with “Lost your password?”. If a cell has a value, that will be the password. Existing users only get a new password if you allow it in More options.

Can I change some values while importing?

Yes, since version 3.1. In the second step, use “Transform the value” under any column to replace a text, add a text before or after, change upper or lower case or set a value for empty cells. You can also add a field with the same value for every user. The preview shows the result before importing.

Can I send a welcome email to the new users?

Yes. The email can be customized in Settings > Mail options, with wildcards for the username, the password, the login URL and any field, and you can send a test email. You can also turn off the automatic emails of WordPress.

How many users can I import?

The import runs in batches, so files with tens of thousands of users can be imported without timeouts. Some users have imported more than 30,000 users at once.

Can I import from a URL or Google Sheets?

Yes. In the first step choose “Use a URL or a file on this server” and paste the link to the CSV, the link of a Google Sheet or a path inside your uploads folder.

Can I schedule automatic imports?

Yes. The Recurring tab imports a file or a URL periodically (hourly, daily, weekly…), so you can keep your users in sync with an external system. The free version has one recurring task, and its file must have the classic format (username in the first column and email in the second one). The Recurring Import add-on adds unlimited tasks, each with its own file, interval, role and notification email, and lets you map the columns of each file like in the import assistant, so it can keep its own column names and order.

The import runs as the user selected in “User that runs the cron”, so it can only do what that user is allowed to do. If the settings are saved by a user who cannot edit other users (edit_users), the import always runs as that same user.

Can I schedule automatic exports?

Yes, with the Recurring Export add-on.

Can I move LearnDash students with their progress?

Yes, with the LearnDash add-on. It exports and imports their groups, enrolled courses, lessons and topics completed, quiz attempts and completed courses with their original dates, using course and lesson titles instead of IDs, so the file also works on a new site and can be filled by hand. Old progress is imported without emailing your students.

Can I delete the users who are not in the file?

Yes, in More options of the third step. You can also change their role instead. The preview tells you how many users will be deleted, and nothing is deleted if the import has errors.

Can I import users without an email address?

WordPress requires an email for every user. The Allow No Email add-on removes that requirement.

Can I import users with custom fields (ACF, BuddyPress, memberships…)?

Yes. Import any custom field matching the column with “Custom field” in the assistant, or using the field name as the column header. ACF, BuddyPress, Paid Memberships Pro, WooCommerce Memberships, WooCommerce Subscriptions and the other plugins listed above have their own integrations.

Can I import users by their WordPress ID?

Yes, with a column matched as “WordPress user ID”. If the ID exists and the username is the same, the user is updated. WordPress does not allow creating users with an ID of your choice, so IDs that do not exist give an error. Use it only if the file comes from the same site.

Can I import serialized data and lists?

Yes. Serialized values are imported as they are. To import a list as an array, separate the items with two colons (::) inside the cell.

Where can I see what was imported?

In the Log tab. History shows the last 100 imports and exports with the user, the file, the result and the errors, Backend shows the detail of the last manual import, and Recurring shows the last recurring import.

I get a “too many redirects” error on my site, how can I solve it?

This is caused by the option that forces the users to reset their password. When it is used, each of those users is redirected to their password page on every page load until they change it, and if that destination cannot be reached (for example, because wp-admin is blocked for customers or subscribers by WooCommerce, by a membership plugin or by a security plugin) the browser ends up in a redirection loop.

Since version 2.4.12 the plugin detects this situation and gives up after 3 consecutive redirects, so the site stays usable, but you can also clear the flag for the users that are already affected: go to the plugin documentation tab and use the button that removes the force reset password metadata from all the users.

If you want to change how many redirects are allowed before the plugin gives up, use the acui_force_reset_password_max_redirects filter (return 0 to disable the limit):

add_filter( 'acui_force_reset_password_max_redirects', function( $max ){ return 5; } );

Which page are the users sent to when I force them to reset their password?

By default they are sent to their WordPress profile page. If WooCommerce or WP User Manager are active, they are sent to the password section of the account page of those plugins instead. You can point them anywhere else using the acui_force_reset_password_edit_profile_url filter, and you can add your own exceptions (pages where the redirection must not happen) using acui_force_reset_password_redirect_condition.

Can you do the import for me?

Yes. At Codection we help you to import, migrate, synchronize or update your users. Write to contacto@codection.com.

How can I report security bugs?

You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. Report a security vulnerability.

This plugin saved me a lot of time. Can I help?

Thank you! A review in wordpress.org helps a lot, and you can also buy us a coffee.

Screenshots

Changelog

3.1.2 – 2026-11-16

  • The loginurl and lostpasswordurl wildcards of the emails take users to the login and lost password pages of Clean Login when it is active and its pages are published, instead of wp-login.php. The new filters acui_login_url and acui_lostpassword_url change them
  • The Send email option of the import shows where the login link of the email goes, and suggests Clean Login, our free plugin, to welcome users on a login page with the look of the site

3.1.1 – 2026-11-15

  • The action acui_post_import_single_user now also receives the row number of the file as last parameter, so addons can add warnings to the right row of the import results
  • The LearnDash help of the documentation tab explains the column course_courseID_access_from more clearly and is hidden when the LearnDash addon is active
  • When LearnDash is active, the Import and Export tabs show what the new LearnDash addon does (move students with their groups, courses, lessons and topics completed, quiz attempts and completion dates). Each user can close it, and a short line stays in the sidebar of the Import tab. Nothing is shown when the addon is active
  • New actions acui_export_start and acui_homepage_sidebar_info to add content at the start of the Export tab and in the sidebar of the Import tab

3.1.0 – 2026-11-12

  • New option in the export to include WooCommerce guest customers, the customers who bought without creating an account. Each guest is exported once per billing email (emails written in upper and lower case are joined), with the billing and shipping details of their last order, the date of their first order as registration date and the customer role. Emails that already belong to a registered user and orders in the trash are skipped, and the date filter is applied to the date of the first order. It works with the new order storage (HPOS) and with the classic one (filters acui_export_guest_emails, acui_export_guest_keys and acui_export_guest_data)
  • The exported file with guest customers can be imported to create an account for each of them: in the import assistant, an empty cell in the username column now uses the email as username, in the same way as when the file has no username column, instead of generating a random username
  • New field “Specific users” in the export to search users by email, username or name and export only them. When it is used, the role and date filters are ignored
  • New options in the export to sort the users by username, user ID, email, display name or registration date, in ascending or descending order. Until now the order could only be changed in the [export-users] shortcode
  • New options in the export to skip a number of rows and to export at most a number of rows, so a big export can be split into several files. They apply to the whole file, guest customers included
  • New column picker in the export: choose between all columns or only some of them, search them, check the ones you want, drag them to change their order and write the name each column will have in the file, without having to write the list by hand. The list is still saved in the same format, so saved settings, the [export-users] shortcode and the Recurring Export addon keep working, and it can still be edited as text (filter acui_export_available_columns)
  • The new export options are saved with the rest of the export settings
  • The messages about the File Formats addon now mention XML files too, which the addon can import since its version 1.0.6
  • New History in Log > History: the last 100 imports and exports (manual, front-end and recurring imports, and exports from the backend and the [export-users] shortcode) with the date, the user, the file, the result (created, updated, deleted and skipped users, or exported rows), the number of errors and warnings, the first 20 messages and the filters used in each export. It can be cleared with a button (filters acui_history_max_entries and acui_history_entry)
  • New transformations in the column mapping of the import assistant, so the file does not have to be edited before importing it: replace a text (for example “España” with “ES” or “cliente” with “customer”), add a text before or after the value (for example “+34” before the phone numbers, not added to empty cells or to values that already have it), convert to upper or lower case, or set a value for the empty cells
  • New option in the import assistant to add a field with the same value for every user, for fields that are not in the file (for example the billing country or a custom field)
  • The preview of the import shows the transformed values and the fields with the same value for every user under the email of each row, so you can check them before importing (filter acui_wizard_mapping)
  • New “File format” option in the export and format attribute in the [export-users] shortcode. CSV is always available and, with the File Formats addon 1.1, also Excel (XLSX), OpenDocument (ODS) and XML. The delimiter is only shown for CSV (filters acui_export_formats and acui_export_convert_file, new methods ACUI_Batch_Exporter::save_export_file() and replace_extension() for the Recurring Export addon)
  • The messages about the Recurring Import addon (Recurring tab, end of an import from a URL or a path, first step of the assistant and readme) now say that it maps the columns of each file like in the import assistant, and the Recurring tab explains that its file must have the classic format and lists the accepted extensions
  • The column mapping of the import assistant can now be reused by other tools: ACUI_Wizard::build_mapped_file() applies a mapping saved by column name (with transformations and fields with the same value for every user) to a file, and ACUI_Wizard::describe_file() returns its columns, examples and suggested fields. The Recurring Import addon 1.1 uses them to map the columns of each task
  • The exported file is now sent from disk instead of being loaded in memory, with its size in the download headers
  • Local paths and URLs to import can also point to XLSX, XLS, ODS or XML files when the File Formats addon is active (until now only .csv was accepted, also in the import assistant and the recurring import). The messages list the accepted extensions

3.0.0 – 2026-11-12

  • New import assistant in five steps: file, columns, options, preview and import. It is the default screen for the import, and the classic screen can be used with the “Switch to classic mode” link (the choice is saved for each user)
  • Column mapping: the columns of the file can have any name and any order. Each column is matched with a WordPress field (username, email, password, names, role, website, registration date, language, user ID…), a WooCommerce billing or shipping field, a custom field with the name you choose, or it can be ignored
  • Explanations under the password, password hash and role fields in the column mapping: what happens with empty cells, with new users and with existing users. A column called password whose values look like encrypted passwords is suggested as a password hash, so they are not imported as plain text passwords by mistake
  • The field of each column can be searched by typing, by its name or by its internal key (for example “city” or “billing_city”), and the key is shown next to each field
  • Automatic detection of the columns by their name in English, Spanish, French, German, Italian and Portuguese, of the email column by its values, and of the classic format with the username in the first column and the email in the second one
  • If the file has no username column, the email can be used as username or a random username can be generated
  • Preview of the import: number of users that will be created, updated or skipped, the rows with errors and the reason, how many users not present in the file will be deleted or have their role changed, and a warning when they will not be deleted because some rows have errors. Nothing is saved until you start the import
  • The rows with errors can be downloaded as a CSV file to fix them and import them again
  • Files that are not saved in UTF-8 (like the CSV files saved by Excel in Windows-1252) are converted, so accents and other special characters are no longer lost when using the assistant
  • Role of new users in the assistant: if a column of the file is imported as role, the assistant says that each user gets the role of that column. If not, you choose between the default role of the site (Settings > General) and one or more roles of your choice, so users can no longer be created without any role by accident when the default role setting was empty
  • The options of the import are grouped in “Main options” (default role, users who already exist, emails and empty cells) and “More options”, which opens automatically if the deletion or the role change of users not present in the file is active
  • When the file comes from a URL or a path on the server, the assistant reminds that it can be imported automatically for free from the Recurring tab, and explains what the Recurring Import addon adds: unlimited tasks, each with its own schedule, role and rules, an email when each run finishes and a list to manage them. The same information appears after an import from a URL or a path. If the addon is already active, both places link to a new recurring import task instead
  • Compatible with the File Formats addon (XLSX, XLS and ODS) and with the Allow No Email addon, which makes the email column optional
  • New filters for developers: acui_wizard_active, acui_wizard_targets, acui_wizard_aliases, acui_wizard_email_required and acui_wizard_file_encoding
  • Clearer choice of where the file comes from: “Upload from your computer”, with an area where you can drag the file and that shows the accepted formats and the chosen file, or “Use a URL or a file on this server”, with examples for a link to a CSV, Google Sheets and a file inside uploads.
  • CSV templates with example data to download from the first step of the import and from the Documentation tab: basic users, WooCommerce customers (when WooCommerce is active) and an empty one with only the headers. They use example.com addresses and the roles of your site, and they open correctly in Excel. Add-ons can add their own templates with the filter acui_csv_templates
  • More robust saving of the uploaded file: if it cannot be moved to the private folder inside uploads, the plugin tries to copy it and then uses a private folder inside the temporary folder of the server. If everything fails, the error shows the folders tried and the real reason given by the server (for example, a full disk quota) instead of “The uploaded file could not be saved”
  • Tools > Site Health: new section in the Info tab with the private folder, the alternative folder, the maximum upload size and the last problem saving an uploaded file (folders tried and messages from the server), and a check in the Status tab that warns when an alternative way had to be used. It can be copied and sent to the hosting provider or to the support forum
  • Clear messages when the upload itself fails: file larger than the maximum upload size (with the limit and what to do), partial upload, missing temporary folder or disk write error
  • Fixed the saved path or URL of the file: anything that was not a URL was turned into a broken URL (for example “http://directly%20a%20file%20from%20your”), and paths with spaces were saved with %20 so the file could not be found. Now only values starting with http:// or https:// are saved as URLs, and broken values saved by previous versions are not shown
  • The test.csv sample file included in the plugin now uses example.com addresses instead of realistic names and emails
  • The styles and scripts of the plugin are now loaded with the date of each file as version, so the browser and the caches always use the latest ones after an update
  • The import screen can now be used on mobile devices: the sidebar is placed below the form on small screens
  • After an import that creates or updates users without errors, a message asks if you want to leave a review on WordPress.org. It can be postponed for 30 days or closed forever, and it is never shown again once you answer (filter acui_show_review_notice)
  • Fixed the message about the Allow No Email addon at the end of an import, which was hidden by the styles of the plugin since version 2.5.11

2.5.14 – 2026-11-11

  • Security: the files of the export in batches and the CSV files uploaded for a manual import are no longer saved in the root of the uploads folder. They are now saved in a private folder with a random name inside uploads, protected with .htaccess, web.config and index files, so they cannot be downloaded from the browser even while the process is running (reported by Ankesh Singh)
  • Security: the names of these files are now random (wp_generate_password) instead of being based on uniqid(), which depends on the time
  • Security: the files left behind by an export or an import that was not finished (closed tab, error in the browser…) are now removed by an hourly scheduled task after 6 hours (filter acui_private_files_max_age). The task also removes the files left in the root of the uploads folder by previous versions, and everything is removed when the plugin is deactivated
  • When a new manual import starts, the file uploaded for the previous import of the same user is removed if it was not finished
  • The path of the uploaded file is no longer sent to the browser during the import
  • The exported file is downloaded with a name that includes the date instead of the internal random name (filter acui_export_download_filename)
  • New option “Export password hashes” in the export screen to choose if the user_pass column with the hashed passwords is included. It is checked by default, so nothing changes if you never saved it. When it is unchecked, user_pass is not exported even if it is in the Columns field. In the shortcode it is the attribute export_password_hashes=”no”, and the filter acui_export_password_hashes can be used too

2.5.13 – 2026-11-01

  • Fixed the recurring import running the first batch again and again without end when the data of the previous batch was not available in the next one, which also made the cron log grow until the settings page could not be loaded. This happened mainly in sites with a persistent object cache, because the batch data was saved in transients
  • The data shared between batches is now saved in a non autoloaded option of each import, which works with or without an object cache, and it is removed when the import ends
  • If the data of the previous batch cannot be found, the import is stopped with an error in the log instead of starting again from the first row
  • The log of each cron run is limited to 1 MB (filter acui_cron_log_max_size) and is no longer autoloaded
  • Manual imports in batches of different users no longer share the same batch data

2.5.12 – 2026-10-30

  • Security: saving the cron task settings now checks every permission before storing anything, so a request that is rejected can no longer leave part of its settings saved
  • Security: when the cron task was configured by a user who cannot promote users, the unattended runs no longer reuse the role permission saved by a previous administrator

2.5.11 – 2026-10-29

  • When some rows are skipped because they have no email, the import result now says how many and that the Allow No Email addon can import them
  • Uploading an XLSX, XLS or ODS file now explains that the File Formats addon can import it, instead of only saying that the file type is not valid
  • The import screen now mentions the Dokan addon when Dokan is active
  • New “Premium addons” section in the plugin description
  • Links to the premium addons now include campaign parameters to know which ones are useful
  • Fewer links in the plugin row of the Plugins screen: the coffee and premium support links are only in the sidebar of the import screen, and the RedSys and Ceca gateways link only appears on sites in Spanish or with a WooCommerce store based in Spain
  • The Import link in the Plugins screen is only shown to users who can import, and the Import and Export links no longer change the order of the other links of the row
  • Fixed a malformed jQuery selector in the users option of Tools > Export

2.5.10 – 2026-10-29

  • Security fix (path traversal and file deletion): the batch importer trusted the file path sent back by the browser on every step, so a user allowed to import users could point it to a CSV outside the uploads folder and read its processed rows in the import log, or have a file whose name contained “acui-import-” deleted when the import finished. The path is now resolved and validated only on the first step and kept on the server for the rest of the batches, and only the temporary file created from an upload is deleted (reported by Rafael Honorato (honorato0))
  • Security fix (SQL injection): the Paid Memberships Pro addons built the query that marks a membership as inactive by concatenating the membership_id column of the CSV. The query is now prepared with integer placeholders (reported by Rafael Honorato (honorato0))
  • Security fix (stored XSS): the from and to attributes of the [export-users] shortcode were checked with a regular expression that only looked for a date anywhere in the value, and the attributes were printed in the hidden fields of the form without escaping, so a contributor could save a post with a from value like 2024-01-01″>
  • Fixed the to attribute of the [export-users] shortcode, which was always ignored because of a typo (reported by dzaku)
  • The [import-users] and [export-users] shortcodes now show a short notice to users who cannot create users instead of stopping the whole page with wp_die(), so a post containing them no longer breaks the page or the REST API for other visitors (reported by dzaku)
  • The acui_export_shortcode_button_text filter now really changes the text of the export button

2.5.9 – 2026-10-23

  • Security fix (privilege escalation): a subscriber could store profile values ending with a NUL byte so that, when a user with import and export permissions exported the users and imported the generated CSV again, the closing quote of that cell was read as escaped and the rest of the value was parsed as new columns and rows, for example a row with their own username and the administrator role. The exporter now removes NUL bytes from every cell and, on PHP 7.4 or newer, the CSV is written and read without escape character (RFC 4180), so a cell can never break out of its quotes
  • Fixed the PHP 8.4+ deprecation notice about the str_getcsv() escape parameter when detecting the delimiter of the CSV file
  • Extra profile fields: new “Keep fields from previous files?” option, when it is checked the columns of a new CSV are added to the list of extra profile fields instead of replacing it, so there is no need to include empty columns for fields that the new users do not use
  • Extra profile fields: every field of the list can now be removed individually, the values already saved for each user are kept

2.5.8

  • New bbPress addon
  • Force password change: when BuddyPress (with the Settings component) or bbPress is active, users are now sent to their front-end settings page (BuddyPress) or profile edit page (bbPress) instead of wp-admin/profile.php, so the back end can stay private. The URL can still be changed with the acui_force_reset_password_edit_profile_url filter
  • Force password change: the flag is now removed whenever the user really changes their password, from any place (BuddyPress settings, bbPress, WooCommerce My Account, the lost password form…), not only from wp-admin/profile.php
  • Force password change: the “Please change your password” notice is also shown on the BuddyPress settings page and the bbPress profile edit page

2.5.7

  • Security fix (account takeover): the 2.5.6 fix closed every role-assignment path, but a user with only create_users could still save the Cron tab with their own “Path or URL of file that is going to be imported” and let the recurring import run with the privileges of an administrator. The scheduled run and “Run now” without session switched to the user selected in “User that runs the cron” (or to the first administrator when none was selected), so every per-user check in the importer passed: a CSV row with an existing administrator’s username and a password reset that account’s password, and the administrator running the cron could be taken over by matching its email and adding a user_email column. The Cron tab now records who saved it, and when that user cannot edit_users the import always runs as that same user (the scheduled run, “Run now” and “Run now” without session), and the “User that runs the cron” selector only offers their own account. “Run now” without session also takes the role-assignment decision from the user who configured the task instead of from the user who clicks the button

2.5.6

  • Security fix (privilege escalation hardening): a user with only create_users could still change other users’ roles without promote_users. Saving the Cron tab now requires promote_users to set “Update roles for existing users?” to anything other than “No” or to enable “Change role of users that are not present in the CSV” (until now only the target role was checked, so the option could be enabled while keeping a previously stored role). The importer also no longer removes the existing roles of updated users when the user running the import cannot assign roles, which previously left them with no role when no role was being assigned

2.5.5

  • The “Update roles for existing users?” option in the Cron import tab is now a selector with the same three choices as the manual importer: “No”, “Yes, update and override existing roles” and “Yes, add new roles and do not override existing ones”. Until now it was a checkbox that could only override the existing roles, so recurring imports had no way to add the roles from the CSV while keeping the ones users already had. Existing settings are kept: a checked box is read as “Yes, update and override existing roles” and an unchecked one as “No”
  • Fixed “Yes, add new roles and do not override existing ones” still replacing the roles of existing users on multisite when the row had no role to assign (no role column and role assignment disabled): the user was re-added to the current site as Subscriber, which removed the roles they already had there. Existing members of the site now keep their roles in that case, and only users that are not yet members of the site are added as Subscriber

2.5.4

  • Security fix (privilege escalation): batched imports (both the manual “Import” tab, which runs in batches once the file is large enough, and the recurring Cron import) resumed the next batch with SplFileObject::seek(), which counts physical lines in the file, while the resume position handed between batches was a count of CSV records. Any exported column whose value can contain a newline — for example the Biographical Info profile field, which is editable by every role and stored verbatim by WordPress core — could make those two counts diverge once such a value was present before the batch boundary. When they diverged, the next batch could resume in the middle of an open quoted field, and the remaining lines that a user had put inside that one cell were then parsed as top-level CSV records in their own right, under the importing administrator’s own role/password-assignment capabilities. The resume position is now the exact byte offset (ftell()/fseek()) at which the last fully parsed CSV record ended, so a batch can only ever resume at a genuine record boundary

2.5.2

  • Security fix (privilege escalation): the role-assignment guards in the importer honoured a caller_can_promote_users value taken straight from the submitted form data instead of checking the current user’s capability. That value is only legitimate on the Action Scheduler cron path, where it is derived from a capability at schedule time; on every request-driven import path (the manual backend importer and the AJAX batch import action the plugin UI uses) the form data is the raw request, so a user with only create_users could add caller_can_promote_users=1 to the request themselves and get the administrator role applied, including to their own account. The pre-recorded decision is now only trusted on the cron path; every request-driven path re-derives it from the current user’s own capabilities (reported by yzx001)
  • Security fix (privilege escalation): the front-end shortcode importer’s “change role of users that are not present in the CSV” feature read the acui_frontend_change_role_not_present / acui_frontend_change_role_not_present_role options with no capability check of its own, and those options could be set by anyone able to reach the settings screen, which is gated only on create_users. A user with only create_users could point the option at administrator and then run the front-end importer to promote every existing editable-role user omitted from the CSV to administrator. Saving those two options now requires promote_users, matching the equivalent Cron tab option, and the front-end import path now also requires promote_users before honouring the option at run time (reported by BINESH MADHARAPU)

2.5.3

  • Fixed the [export-users] shortcode’s columns attribute whitelist (added in 2.5.1 to allow the key=>Label renaming syntax) still stripping the whole attribute to empty when the custom label contained accented or other non-ASCII letters (for example columns="first_name=>Prénom"), since the whitelist only matched plain ASCII letters

2.5.1

  • Fixed the [export-users] shortcode dropping the columns attribute when it used the key=>Label renaming syntax (for example columns="user_email=>Email,first_name=>First name"), which caused all columns to be exported instead of just the selected ones. The = and > characters were not part of the shortcode attribute’s whitelist and made it get sanitized down to an empty value

2.5

  • Security hardening: exporting users is now gated by its own acui_export_capability filter (default edit_users) instead of sharing the acui_capability filter used by import. Previously, any site that lowered acui_capability to give a role import-only access (for example, to add_users) was also handing that same role access to the Export tab and its download/save endpoints, since both checks resolved to the exact same filter call with no way to tell them apart. The Export tab, its nav link, the plugin list “Export” action link and the export AJAX/download handlers now check the new filter independently, so an import-only role stays import-only unless the new filter is explicitly overridden
  • The “Update existing users?” section on the Import tab now hides the “Update emails?”, “Update roles for existing users?” and “Update passwords for existing users?” fields when “Update existing users?” is set to “No”, since they have no effect in that case

2.4.18

  • Security fix (privilege escalation): the CSV exporter writes fields with the NUL character as the escape character (fputcsv(..., '"', "\0")), but the importer’s SplFileObject::fgetcsv() calls were passing only the delimiter, which silently kept PHP’s default backslash escape character. Any registered user able to save their own profile could set display_name to a value ending in a comma and a backslash (e.g. a,\) and nickname to a value starting and ending with a comma around a role name (e.g. ,administrator,q). When an administrator later used the plugin’s own Export tab and re-imported that file with “Update existing users” and “Update roles for existing users” both set to “yes” — the plugin’s documented backup/migration workflow — the escape mismatch merged the display_name cell into the role column and split the nickname cell, so the parsed role column for the attacker’s own row read exactly administrator, and the administrator’s own authorized import call applied it. The importer’s fgetcsv() calls now use the same explicit escape character as the exporter, so no combination of profile field values can shift the parsed column boundaries
  • Security fix (hardening): as defense in depth for the same code path, assigning the administrator role during an import now additionally requires the create_users capability (not only promote_users) on the account running the import. This does not change behavior on sites using the plugin’s own default access gate, but stops a future column-shift bug — or a site that has lowered the acui_capability filter to allow non-administrators to run imports — from being able to deliver an administrator role assignment through a CSV. Other roles present on the same row are unaffected; only administrator is dropped (with a warning) when create_users is missing

2.4.17

  • Security fix (privilege escalation): the 2.4.16 fix only closed the literal acui_fire_cron_no_session no-session action; it did not close the same gap on a genuinely unattended run of the recurring import (an Action Scheduler queue tick, with no $caller_can_promote_users argument at all). A …