# CVE-2026-10038: Missing authorization in Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More

> Authenticated attackers can delete arbitrary media library attachments by exploiting an insecure direct object reference in the avatar update flow.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-9jf2-67mg-r5ph

## What is CVE-2026-10038?

CVE-2026-10038 is a medium-severity missing authorization vulnerability in smub Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More plugin for WordPress is vulnerable to Insecure Direct Object Reference / Authorization Bypass leading to Arbitrary Attachment Deletion in versions up to, and including, 1.8.11.1 via the profile avatar update flow. This is due to the save_avatar() function in Charitable_Profile_Form calling wp_delete_attachment() on an attachment ID read from the user's 'avatar' meta without validating that the attachment is owned by the user, combined with Charitable_Data_Processor::process_picture() returning the raw posted value when no file is uploaded, allowing the 'avatar' user meta to be poisoned with any attacker-chosen attachment ID. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary attachments from the Media Library by performing a two-request chain (first poisoning the stored avatar meta value with a target attachment ID, then triggering deletion via a normal avatar upload).

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

## Which versions are affected by CVE-2026-10038?


## How do I fix CVE-2026-10038?

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

## Is CVE-2026-10038 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10038 and fix it if it is affected.

What it is: CVE-2026-10038 is a medium-severity missing authorization vulnerability in smub Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10038 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-2026-10038/ (Markdown: https://insights.sbomify.com/CVE-2026-10038/index.md)
```

## Sources

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

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