CVE-2026-3629

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-03-22. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-14256 (ENISA EUVD) · GHSA-974q-2m48-3288 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Wordfence) lists carazo Import and export users and customers versions up to and including 1.29.7 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 21, 2026

Last Modified

June 17, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 228 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-31 17:18 UTCEG score recompute
  3. 2026-10-31 17:18 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-25 14:32 UTCEG score recompute
  12. 2026-10-25 05:19 UTCEG score recompute
  13. 2026-10-25 05:19 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-10-18 17:28 UTCEG score recompute
  21. 2026-10-18 17:28 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-10-18 16:51 UTCEG score recompute
  23. 2026-10-18 16:51 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  25. 2026-10-18 03:44 UTCEG score recompute
Show 74 more
  1. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-17 15:17 UTCEG score recompute
  3. 2026-10-17 15:17 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-12 16:11 UTCEG score recompute
  10. 2026-10-11 19:53 UTCEG score recompute
  11. 2026-10-11 17:06 UTCEG score recompute
  12. 2026-10-11 14:33 UTCEG score recompute
  13. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  29. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  33. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  35. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  36. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  37. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  38. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  40. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  41. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  43. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  44. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  45. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  47. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  48. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  50. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  51. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  56. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  57. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  58. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  59. 2026-08-16 10:53 UTCEG score recompute
  60. 2026-08-16 10:53 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  62. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  63. 2026-08-14 20:03 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  64. 2026-08-14 07:04 UTCEG score recompute
  65. 2026-08-14 07:04 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  67. 2026-08-12 21:45 UTCEG score recompute
  68. 2026-08-12 21:45 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  69. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  70. 2026-08-11 21:17 UTCEG score recompute
  71. 2026-08-11 21:17 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1
  72. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  73. 2026-08-11 04:20 UTCEG score recompute
  74. 2026-08-11 04:20 UTCGHSA enrichmentGHSA-974q-2m48-3288 · GitHub severity HIGH · GitHub CVSS 8.1

Public detection checks

(1 reference)

A public detection check is referenced for this CVE (1 GitHub checker repository). A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code.

  • GitHub checkerPySecTools/CVE-2026-3629
    Published May 17, 2026

    WordPress Privilege Escalation Checker

    Open source ↗

Frequently asked(5)

What is CVE-2026-3629?
CVE-2026-3629 is a high-severity vulnerability; its CVE record was published on March 21, 2026. 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…
When was the CVE record for CVE-2026-3629 published?
The CVE record for CVE-2026-3629 was published on March 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-3629 actively exploited?
CVE-2026-3629 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3629?
CVE-2026-3629 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-3629?
No fix for CVE-2026-3629 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (Wordfence) lists carazo Import and export users and customers versions up to and including 1.29.7 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3629

Explore →

Is Your Infrastructure Affected by CVE-2026-3629?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.