CVE-2025-2331

GiveWP – Donation Plugin and Fundraising Platform <= 3.22.1 - Authenticated (Subscriber+) Sensitive Information Exposure

Strategic Overview

Status
Patched in 3.22.2
Affected Version
<= 3.22.1
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-2331
View all GiveWP – Donation Plugin and Fundraising Platform vulnerabilities

At a glance

CVE-2025-2331 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the GiveWP WordPress plugin, affecting versions <= 3.22.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.22.2; sites on affected versions should update now. Disclosed March 2025, reported by Brian Sans-Souci (liardom).

Vulnerability Overview

The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.22.1 via a misconfigured capability check in the 'permissionsCheck' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive data including reports detailing donors and donation amounts.

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 privileges on the target site, and no interaction from a victim user.

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

GiveWP <= 3.22.1 carries this weakness at permissionsCheck, 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 GiveWP the fix is 3.22.2: builds <= 3.22.1 are affected, anything from 3.22.2 onward is not.

Remediation

Update to version 3.22.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: GiveWP 3.22.2 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