# CVE-2026-7641: Privilege escalation in Import and export users and customers

> Authenticated subscribers can escalate to Administrator on WordPress Multisite subsites due to incomplete meta key blocklisting in the Import and export users plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-3v5c-rmm5-g74r

## What is CVE-2026-7641?

CVE-2026-7641 is a high-severity vulnerability in carazo Import and export users and customers, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-7641?


## How do I fix CVE-2026-7641?

No fix has been published for CVE-2026-7641 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7641 being exploited?

There is no known exploitation of CVE-2026-7641 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7641 and fix it if it is affected.

What it is: CVE-2026-7641 is a high-severity vulnerability in carazo Import and export users and customers, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7641 in the wild and no public exploit code.

Affected product: carazo Import and export users and customers. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7641/ (Markdown: https://insights.sbomify.com/CVE-2026-7641/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7641
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7641
- OSV: https://osv.dev/vulnerability/CVE-2026-7641

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7641/
Summaries are generated and may contain mistakes; the official description above is the record.