Charitable <= 1.8.11.1 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Attachment Deletion via 'avatar' Parameter
Strategic Overview
- Status
- Patched in 1.8.11.2
- Affected Plugin
- Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns)
- Affected Version
<= 1.8.11.1- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-10038
At a glance
CVE-2026-10038 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Charitable WordPress plugin, affecting versions <= 1.8.11.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.8.11.2; sites on affected versions should update now. Disclosed June 2026, reported by Khanh Nguyen.
Vulnerability Overview
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).
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Charitable <= 1.8.11.1 carries this weakness at avatar, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Charitable the fix is 1.8.11.2: builds <= 1.8.11.1 are affected, anything from 1.8.11.2 onward is not.
Remediation
Update to version 1.8.11.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Charitable 1.8.11.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns)
- 9.8CVE-2023-4404: Donation Forms by Charitable Privilege Escalation
CVE-2023-4404 - 7.2Charitable – Donation Plugin <= 1.6.50 Stored Cross-Site Scripting
- 6.5CVE-2026-7619: Charitable <= 1.8.10.4 SQL Injection
CVE-2026-7619 - 6.5CVE-2025-11893: Charitable SQL Injection
CVE-2025-11893 - 6.4CVE-2025-30770: Charitable <= 1.8.4.7 Stored Cross-Site Scripting
CVE-2025-30770 - 6.4CVE-2023-47816: Charitable <= 1.7.0.13 Stored Cross-Site Scripting
CVE-2023-47816 - 6.4CVE-2021-24531: Charitable – Donation Plugin <= 1.6.50 Stored XSS
CVE-2021-24531 - 6.1CVE-2024-10876: Charitable Reflected XSS
CVE-2024-10876
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C