CVE-2025-4522 json
IDonate 2.0.0 - 2.1.9 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary User Deletion via admin_post_donor_delete Function
published 2025-11-07 12 mo ago modified 2026-10-07 32 d ago also EUVD-2025-38237
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- themeatelier idonate 2.1.10
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12 mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- themeatelier IDonate – Blood Donation, Request And Donor Management System
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/bb0625ec-5ac9-4896-ac11-87fc9287f68a?source=cve
patch, third-party-advisory
-
plugins.trac.wordpress.org
/changeset/3334424/idonate/tags/2.1.10/src/Helpers/DonorFunctions.php?old=3279142&old_path=idonate%2Ftags%2F2.
patch
-
wordpress.org
/plugins/idonate/#developers
release-notes
-
plugins.trac.wordpress.org
/browser/idonate/tags/2.1.9/src/Helpers/DonorFunctions.php#L658
product
-
plugins.trac.wordpress.org
/browser/idonate/tags/2.1.9/src/Admin/Admin.php#L75
product
Sources
- CVE List CVE-2025-4522
- NVD CVE-2025-4522
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.