mediumCVE-2026-15026

Import and export users and customers <= 2.4.0 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via email_template_selected AJAX Action

Q: What is affected by CVE-2026-15026?

Import and export users and customers versions listed as affected should be reviewed: *-2.4.0.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

The Import and export users and customers plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.4.0 via the email_template_selected. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract the post_title and raw post_content of arbitrary posts regardless of status (draft, private, future, trash, password-protected) or post type (including non-public CPTs such as WooCommerce orders and internal CRM records) by enumerating post IDs. The required codection-security nonce is exposed as inline JavaScript on any wp-admin page when ?post_type=acui_email_template is appended to the URL, which is reachable by any authenticated user including Subscribers.

ProductImport and export users and customers

CVSS4.3

EPSS0.00223

UpdatedJuly 13, 2026

Quick answer

Import and export users and customers should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-2.4.0

Fixed versions

2.4.1

How to fix it

Import and export users and customers is affected by CVE-2026-15026, a authorization bypass issue in versions up to 2.4.0. Wordfence lists the official remediation as updating to version 2.4.1, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, WooCommerce checkout/account/vendor flows, Elementor/page-builder surfaces, reservation or booking workflows, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has Import and export users and customers installed, including production, staging, multisite, client, WooCommerce, marketplace, and booking environments.
Confirm the installed Import and export users and customers version and compare it with the affected range from the Wordfence advisory.
Update Import and export users and customers to version 2.4.1, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable Import and export users and customers or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review affected REST endpoints, AJAX actions, roles, capabilities, account changes, orders, bookings, payments, marketplace vendor actions, and admin actions for unauthorized activity.
Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running Import and export users and customers version is version 2.4.1 or newer, and record the patched version in the remediation ticket.
Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, account, vendor, payment, booking, invoice, or settings change.
Review web server, WordPress, security plugin, WAF, database, WooCommerce, and application logs for exploitation attempts before and after the fix.
Retest normal visitor, subscriber, customer, vendor, editor, administrator, checkout, form, API, booking, reservation, invoice, or integration workflows to confirm expected behavior still works.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress WooCommerce Authorization Bypass Information Disclosure

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-15026?

Import and export users and customers versions listed as affected should be reviewed: *-2.4.0.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.