# CVE-2021-34646: Booster for WooCommerce <= 5.4.3 Authentication Bypass

> Attackers can bypass authentication and log in as any user, including administrators, due to weak token generation in the email verification module.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 30 Aug 2021
- **Updated:** 5 May 2025
- **Also known as:** GHSA-q3w8-grp4-hc32

## What is CVE-2021-34646?

CVE-2021-34646 is a critical authentication bypass vulnerability in Pluggabl LLC Booster for WooCommcerce, published on 30 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2021-34646?

It affects 1 product.


Products: Booster Booster for Woocommerce.

## How do I fix CVE-2021-34646?

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

## Is CVE-2021-34646 being exploited?

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

Public exploit code:

- CVE-2021-34646 PoC (github_poc): https://github.com/motikan2010/CVE-2021-34646
- PoC for CVE-2021-34646 (github_poc): https://github.com/0xB455/CVE-2021-34646
- WordPress Plugin WooCommerce Booster Plugin 5.4.3 - Authentication Bypass (exploitdb)

## Other vulnerabilities in Pluggabl LLC Booster for WooCommcerce

- [CVE-2024-1986](https://insights.sbomify.com/CVE-2024-1986/): Elite Booster for WooCommerce <= 7.1.7 - Authenticated (Subscriber+) Arbitrary File Upload (high 8.8)
- [CVE-2024-13342](https://insights.sbomify.com/CVE-2024-13342/): Booster for WooCommerce <= 7.2.4 - Unauthenticated Double Extension Arbitrary File Upload (high 8.1)
- [CVE-2024-13744](https://insights.sbomify.com/CVE-2024-13744/): Booster for WooCommerce 4.0.1 - 7.2.4 - Unauthenticated Arbitrary File Upload (high 8.1)
- [CVE-2022-3763](https://insights.sbomify.com/CVE-2022-3763/): Booster for WooCommerce - Checkout Files Deletion via CSRF (high 8.1)
- [CVE-2024-13708](https://insights.sbomify.com/CVE-2024-13708/): Booster for WooCommerce 4.0.1 - 7.2.4 - Unauthenticated Stored Cross-Site Scripting (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34646 and fix it if it is affected.

What it is: CVE-2021-34646 is a critical authentication bypass vulnerability in Pluggabl LLC Booster for WooCommcerce, published on 30 Aug 2021. 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-2021-34646 in the wild and no public exploit code.

Affected product: Pluggabl LLC Booster for WooCommcerce. 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-2021-34646/ (Markdown: https://insights.sbomify.com/CVE-2021-34646/index.md)
```

## Sources

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

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