# CVE-2024-4185: Auth bypass in Customer Email Verification for WooCommerce

> Unauthenticated attackers can bypass email verification and potentially user authentication due to insufficient randomness in activation codes.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7fhm-gx9f-8c93

## What is CVE-2024-4185?

CVE-2024-4185 is a high-severity authentication bypass vulnerability in wpcodefactory Customer Email Verification for WooCommerce, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Email Verification and Authentication Bypass in all versions up to, and including, 2.7.4 via the use of insufficiently random activation code. This makes it possible for unauthenticated attackers to bypass the email verification, and if both the "Login the user automatically after the account is verified" and "Verify account for current users" options are checked, then it potentially makes it possible for attackers to bypass authentication for other users.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2024-4185?


## How do I fix CVE-2024-4185?

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

## Is CVE-2024-4185 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4185 and fix it if it is affected.

What it is: CVE-2024-4185 is a high-severity authentication bypass vulnerability in wpcodefactory Customer Email Verification for WooCommerce, published on 30 Apr 2024. 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-2024-4185 in the wild and no public exploit code.

Affected product: wpcodefactory Customer Email Verification for WooCommerce. 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-2024-4185/ (Markdown: https://insights.sbomify.com/CVE-2024-4185/index.md)
```

## Sources

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

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