CVE-2026-92540

Import and export users and customers <= 2.5.1 - Authenticated (Admin+) Privilege Escalation

2026-09-18 00:00
yzx001

Strategic Overview

Status
Patched in 2.5.2
Affected Version
<= 2.5.1
CVSS
7.2High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-92540
View all Import and export users and customers vulnerabilities

At a glance

CVE-2026-92540 is a high-severity Improper Privilege Management vulnerability in the Import and export users and customers WordPress plugin, affecting versions <= 2.5.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 2.5.2; sites on affected versions should update now. Disclosed September 2026, reported by yzx001.

Vulnerability Overview

The Import and export users and customers plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.5.1. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for authenticated attackers, with admin-level access and above, to elevate their privileges on multi-site instances.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

Reaching this weakness in Import and export users and customers <= 2.5.1 takes an account at Admin level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Import and export users and customers the fix is 2.5.2: builds <= 2.5.1 are affected, anything from 2.5.2 onward is not.

Remediation

Update to version 2.5.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Import and export users and customers 2.5.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C