Charitable Donation - Broken Access Control (CVE-2026-10038)

Q: Am I affected by this vulnerability?

You are affected if your site runs Charitable Donation.

Q: How do I fix it?

Update Charitable Donation to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

Q: What can an attacker actually do?

This is a Broken Access Control flaw. An attacker who exploits it can reach actions or data that should have been restricted to someone else.

CVE-2026-10038

Vulnerability CVE-2026-10038 PLUGIN charitable-donation MEDIUM

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).

CVE-2026-10038

MEDIUM CVSS 4.3 Published 2026-06-06 Updated 2026-07-23

AI Risk Moderate (38/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P4 Planned

Severity Band MEDIUM

CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected Components 2

Reference Links 10

AI Risk Engine Moderate (38/100)

Exploitability Low

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-06-06 CVE published and first recorded in the threat feed.
2026-07-23 Record updated with latest vulnerability metadata.
2026-06-06 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 107 days ago

AI enriched 107 days ago (2026-06-06 22:11 UTC)

Technical Summary

Potential Impact

Severity is MEDIUM (CVSS 4.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 38/100 (Moderate, Low) with priority P4 Planned. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Charitable Donation PLUGIN · charitable-donation Affected: >= 0, <= 1.8.11.1 Fixed version not specified

Fundraising with Recurring Donations & More PLUGIN · fundraising-with-recurring-donations-more Affected range not specified Fixed version not specified

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Charitable Donation to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Charitable Donation, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?