dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-7641

HIGH · 8.8 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Import and export users and customers plugin for WordPress is vulnerable to Privilege Escalation in all versions up to and including 2.0.8 via the `save_extra_user_profile_fields()` function. This is due to an incomplete blocklist that correctly restricts capability meta keys for the primary site (e.g., `wp_capabilities`, `wp_user_level`) but fails to block the equivalent meta keys for any other subsite in a WordPress Multisite network (e.g., `wp_2_capabilities`, `wp_2_user_level`), allowing these keys to pass the `in_array()` check and be written directly to user meta via `update_user_meta()`. This makes it possible for authenticated attackers, with Subscriber-level access and above, to escalate their privileges to Administrator on any subsite within the Multisite network by submitting a crafted profile update to `/wp-admin/profile.php`. Exploitation requires that an administrator has previously imported a CSV file containing multisite-prefixed capability column headers and has enabled the 'Show fields in profile?' option, which causes those keys to be stored in the `acui_columns` option and exposed as editable fields on the user profile page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Import and export users and customers WordPress plugin has an incomplete blocklist in the save_extra_user_profile_fields() function that blocks primary site capability meta keys (wp_capabilities, wp_user_level) but fails to block multisite-prefixed equivalents (wp_2_capabilities, wp_2_user_level). This allows authenticated attackers with Subscriber-level access to write arbitrary capability meta to user profiles, escalating their privileges to Administrator on any subsite.

MitigationDisable the 'Show fields in profile?' option immediately and update to version 2.0.9 or later when available; review user meta for unauthorized capability grants on affected subsites.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WordPress multisite installation
    Check wp-config.php for define( 'MULTISITE', true ); or query the wp_site table in the database
    Affected if MULTISITE is true - the vulnerability only affects multisite installations
  2. Verify the plugin is installed
    Check the WordPress plugins directory or query wp_plugins table for 'import-and-export-users-and-customers' or 'Import and export users and customers'
    Affected if Plugin is installed and active on a multisite setup
  3. Check plugin version
    Query wp_options for option_name='ieuc_plugin_version' or inspect the plugin file header in wp-content/plugins/import-and-export-users-and-customers/import-export-users.php
    Affected if Version is unknown or below 2.0.9 (the patched version)
  4. Check if vulnerable option is enabled
    Query wp_options for option_name='ieuc_show_fields' with option_value='1', or check the plugin settings page under Users > Import Export Users
    Affected if 'Show fields in profile?' option is enabled (value=1)
  5. Inspect user meta for unauthorized capability grants
    Query wp_usermeta for meta_key patterns like 'wp_%_capabilities' where the capability value includes 'administrator', or manually review user profiles in Network Admin > Users for unexpected admin roles
    Affected if Any user (especially Subscriber-level) has wp_X_capabilities meta containing administrator role

A user is affected if running WordPress multisite with the plugin installed, the 'Show fields in profile?' option enabled, and a version below 2.0.9 where unauthorized capability meta exists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the 'Show fields in profile?' option immediately and update to version 2.0.9 or later when available; review user meta for unauthorized capability grants on affected subsites.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7641 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data