CVE-2021-34646

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2021-21296 (ENISA EUVD) · GHSA-q3w8-grp4-hc32 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 51%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 51%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

Update to version 5.4.4 or newer (from the CVE record's solution, Wordfence) — apply it.

Versions up to, and including, 5.4.3, of the Booster for WooCommerce WordPress plugin are vulnerable to authentication bypass via the process_email_verification function due to a random token generation weakness in the reset_and_mail_activation_link function found in the ~/includes/class-wcj-emails-verification.php file. This allows attackers to impersonate users and trigger an email address verification for arbitrary accounts, including administrative accounts, and automatically be logged in as that user, including any site administrators. This requires the Email Verification module to be active in the plugin and the Login User After Successful Verification setting to be enabled, which it is by default.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
79
EG Risk 79/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation51% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: Update to version 5.4.4 or newer (from the CVE record's solution, Wordfence). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
51%
EPSS %ILE
98th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
51% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.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; Attend at high (mission-essential systems).

Update to version 5.4.4 or newer (from the CVE record's solution, Wordfence). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 30, 2021

Last Modified

November 21, 2024

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 54× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 233 rows 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. None are among the latest 100 rows. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-50299
    Published Sep 17, 2021

    WordPress Plugin WooCommerce Booster Plugin 5.4.3 - Authentication Bypass

    Open source ↗
  • GitHub PoCmotikan2010/CVE-2021-34646
    Published Sep 4, 2021

    CVE-2021-34646 PoC

    Open source ↗

Frequently asked(5)

What is CVE-2021-34646?
CVE-2021-34646 is a critical-severity vulnerability; its CVE record was published on August 30, 2021. Versions up to, and including, 5.4.3, of the Booster for WooCommerce WordPress plugin are vulnerable to authentication bypass via the process_email_verification function due to a random token generation weakness in the reset_and_mail_activation_link function found in the…
When was CVE-2021-34646 made public?
CVE-2021-34646 was made public on August 24, 2021: that is the date its CVE record's CNA, Wordfence, gives for when the vulnerability was made public. The CVE record itself was published on August 30, 2021. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2021-34646 actively exploited?
CVE-2021-34646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-34646?
CVE-2021-34646 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2021-34646?
The CVE record's solution for CVE-2021-34646, written by its CNA Wordfence, names the fix: "Update to version 5.4.4 or newer."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-34646

Explore →

Is Your Infrastructure Affected by CVE-2021-34646?

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