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

> Unauthenticated attackers can escalate privileges to Administrator via crafted registration requests if specific plugin settings are enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-974q-2m48-3288

## What is CVE-2026-3629?

CVE-2026-3629 is a high-severity vulnerability in carazo Import and export users and customers, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, 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, 1.29.7. This is due to the 'save_extra_user_profile_fields' function not properly restricting which user meta keys can be updated via profile fields. The 'get_restricted_fields' method does not include sensitive meta keys such as 'wp_capabilities'. This makes it possible for unauthenticated attackers to escalate their privileges to Administrator by submitting a crafted registration request that sets the 'wp_capabilities' meta key. The vulnerability can only be exploited if the "Show fields in profile" setting is enabled and a CSV with a wp_capabilities column header has been previously imported.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-3629 being exploited?

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

Public exploit code:

- WordPress Privilege Escalation Checker (github_poc): https://github.com/PySecTools/CVE-2026-3629

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3629 is a high-severity vulnerability in carazo Import and export users and customers, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3629 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-3629/ (Markdown: https://insights.sbomify.com/CVE-2026-3629/index.md)
```

## Sources

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

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