CVE-2025-4523

IDonate 2.0.0 - 2.1.9 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via admin_donor_profile_view Function

2025-07-31 16:22
kr0d

Strategic Overview

Status
Patched in 2.1.10
Affected Version
2.0.0 – 2.1.9
CVSS
6.5Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-4523
View all IDonate – Blood Donation, Request And Donor Management System vulnerabilities

At a glance

CVE-2025-4523 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor 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 confidentiality 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 July 2025, reported by kr0d.

Vulnerability Overview

The IDonate – Blood Donation, Request And Donor Management System plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the admin_donor_profile_view() function in versions 2.0.0 to 2.1.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to expose an administrator’s username, email address, and all donor fields.

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

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

IDonate 2.0.0 – 2.1.9 carries this weakness at admin_donor_profile_view(), and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. 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?

The fix is the thing that ends this: IDonate 2.1.10 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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