CVE-2025-4522

IDonate 2.0.0 - 2.1.9 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary User Deletion via admin_post_donor_delete Function

2025-11-06 15:39
kr0d

Strategic Overview

Status
Patched in 2.1.10
Affected Version
2.0.0 – 2.1.9
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-4522
View all IDonate – Blood Donation, Request And Donor Management System vulnerabilities

At a glance

CVE-2025-4522 is a medium-severity Missing Authorization vulnerability in the IDonate WordPress plugin, affecting versions 2.0.0 – 2.1.9. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.10; sites on affected versions should update now. Disclosed November 2025, reported by kr0d.

Vulnerability Overview

The IDonate – Blood Donation, Request And Donor Management System plugin for WordPress is vulnerable to Insecure Direct Object Reference via the admin_post_donor_delete() function in versions 2.0.0 to 2.1.9. By supplying an arbitrary user_id parameter value to the wp_delete_user() function, authenticated attackers, with Subscriber-level access and above could delete arbitrary user accounts, including those of administrators.

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. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

IDonate 2.0.0 – 2.1.9 carries this weakness at admin_post_donor_delete(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For IDonate the fix is 2.1.10: builds 2.0.0 – 2.1.9 are affected, anything from 2.1.10 onward is not.

Remediation

Update to version 2.1.10, 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: IDonate 2.1.10 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C