# CVE-2024-8292: Auth bypass in WP-Recall – Registration, Profile, Commerce & More

> Unauthenticated attackers can update arbitrary user passwords via insecure direct object reference in the WP-Recall plugin when the commerce addon is enabled.

- **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:** 6 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r29w-mcfc-r8cc

## What is CVE-2024-8292?

CVE-2024-8292 is a critical authentication bypass vulnerability in wppost WP-Recall – Registration, Profile, Commerce & More, published on 6 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to privilege escalation/account takeover in all versions up to, and including, 16.26.8. This is due to to plugin not properly verifying a user's identity during new order creation. This makes it possible for unauthenticated attackers to supply any email through the user_email field and update the password for that user during new order creation. This requires the commerce addon to be enabled in order to exploit.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Plechevandrey Wp-Recall.

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

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

## Is CVE-2024-8292 being exploited?

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

## Other vulnerabilities in wppost WP-Recall – Registration, Profile, Commerce & More

- [CVE-2025-1323](https://insights.sbomify.com/CVE-2025-1323/): WP-Recall – Registration, Profile, Commerce & More <= 16.26.10 - Unauthenticated SQL Injection (high 7.5)
- [CVE-2025-1324](https://insights.sbomify.com/CVE-2025-1324/): Cross-site scripting in WP-Recall – Registration, Profile, Commerce & More (medium 6.4)
- [CVE-2025-1325](https://insights.sbomify.com/CVE-2025-1325/): Missing authorization in WP-Recall – Registration, Profile, Commerce & More (medium 6.3)
- [CVE-2024-1175](https://insights.sbomify.com/CVE-2024-1175/): WP-Recall – Registration, Profile, Commerce & More <= 16.26.6 - Unauthenticated Payment Deletion via delete_payment (medium 5.3)
- [CVE-2024-9770](https://insights.sbomify.com/CVE-2024-9770/): WP-Recall < 16.26.12 - Admin+ SQL Injection (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8292 is a critical authentication bypass vulnerability in wppost WP-Recall – Registration, Profile, Commerce & More, published on 6 Sep 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-8292 in the wild and no public exploit code.

Affected product: wppost WP-Recall – Registration, Profile, Commerce & More. 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-8292/ (Markdown: https://insights.sbomify.com/CVE-2024-8292/index.md)
```

## Sources

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

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