dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-3629

HIGH · 8.1 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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, 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.

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 plugin for WordPress fails to restrict sensitive user meta keys during profile field updates. The get_restricted_fields method does not include wp_capabilities, allowing unauthenticated attackers to craft registration requests that set this meta key and escalate to Administrator privileges.

MitigationUpdate the plugin to version 1.29.8 or later. As a fallback, disable the 'Show fields in profile' setting and audit for any previously imported CSV files containing wp_capabilities columns.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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. Verify plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Import and export users and customers'
    Affected if Plugin is installed and active
  2. Check plugin version
    Click on the plugin name or view details to see the installed version number
    Affected if Version is lower than 1.29.8 or the version cannot be determined (plugin is vulnerable)
  3. Inspect restricted fields configuration
    Go to plugin settings > Profile Fields or 'Show fields in profile' setting area. Locate the get_restricted_fields method or configuration where meta keys are defined for restriction
    Affected if wp_capabilities is NOT listed among the restricted/restricted_meta_keys or the configuration is missing this field entirely
  4. Review CSV import history
    Check plugin logs, audit logs, or imported CSV files for any past imports that may have contained a wp_capabilities or capabilities column
    Affected if Any previous CSV imports included wp_capabilities data and were processed by this plugin
  5. Check for unexpected admin accounts
    Navigate to Users > All Users in WordPress admin and review user accounts with Administrator role, especially any that appear unexpected or were created around the time of CSV imports
    Affected if Unexpected administrator accounts exist that were not intentionally created

User is affected if the Import and export users and customers plugin is installed with a version prior to 1.29.8 and the wp_capabilities field is not properly restricted in the plugin configuration.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.29.8 or later. As a fallback, disable the 'Show fields in profile' setting and audit for any previously imported CSV files containing wp_capabilities columns.

Recommended fix High confidence

Update to version 1.29.8 or later (latest available version)

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Find 'Import and export users and customers' plugin and update to the latest available version
  3. After updating, go to the plugin settings and verify the 'Show fields in profile' setting is disabled or properly restricted
  4. Review existing user accounts, especially any newly created Administrator accounts, to confirm no unauthorized privilege escalation occurred
  5. If any suspicious Administrator accounts exist, remove them immediately

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3629 — 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-3629 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