CVE-2026-3629
Unauthenticated privilege escalation in WP plugin via wp_capabilities key.
Is CVE-2026-3629 being exploited?
Not confirmed. CVE-2026-3629 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-3629?
CVE-2026-3629 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-3629?
Not known from our data. No patch reference has been recorded for CVE-2026-3629, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-3629 affect?
CVE-2026-3629 affects WordPress plugin: Import and export users and customers (≤1.29.7). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-3629?
Patch/update when available; disable Show fields in profile; review CSV imports.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Admin privileges via crafted registration; requires Show fields in profile and CSV header.
Patch when possible
- affected<= 1.29.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.