# CVE-2024-8791: Auth bypass in Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More

> Unauthenticated attackers can update arbitrary user credentials, including administrators, leading to account takeover and privilege escalation.

- **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:** 24 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g3q3-27w2-fgmp

## What is CVE-2024-8791?

CVE-2024-8791 is a critical authentication bypass vulnerability in smub Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More, published on 24 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Donation Forms by Charitable – Donations Plugin & Fundraising Platform for WordPress plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.8.1.14. This is due to the plugin not properly verifying a user's identity when the ID parameter is supplied through the update_core_user() function. This makes it possible for unauthenticated attackers to update the email address and password of arbitrary user accounts, including administrators, which can then be used to log in to those user accounts.

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

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

It affects 1 product.


Products: Wpcharitable Charitable.

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

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

## Is CVE-2024-8791 being exploited?

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

## Other vulnerabilities in smub Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More

- [CVE-2023-4404](https://insights.sbomify.com/CVE-2023-4404/): Donation Forms by Charitable <= 1.7.0.12 - Unauthenticated Privilege Escalation (critical 9.8)
- [CVE-2018-21011](https://insights.sbomify.com/CVE-2018-21011/): Information disclosure in n/a (high 7.5)
- [CVE-2022-47441](https://insights.sbomify.com/CVE-2022-47441/): WordPress Charitable Plugin <= 1.7.0.10 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2023-47816](https://insights.sbomify.com/CVE-2023-47816/): WordPress Charitable Plugin <= 1.7.0.13 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2021-24531](https://insights.sbomify.com/CVE-2021-24531/): Charitable – Donation Plugin < 1.6.51 - Authenticated Stored Cross-Site Scripting (XSS) (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8791 is a critical authentication bypass vulnerability in smub Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More, published on 24 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-8791 in the wild and no public exploit code.

Affected product: smub Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & 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-8791/ (Markdown: https://insights.sbomify.com/CVE-2024-8791/index.md)
```

## Sources

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

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