dbcve.org
GivewpWordPress extension

CVE-2025-2331

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-22
Fix available
A fix is available. Upgrade to 3.22.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GiveWP WordPress plugin has a misconfigured capability check in its 'permissionsCheck' function that allows authenticated users with Subscriber-level access (the lowest privilege tier) to bypass authorization and access sensitive donation reports containing donor names and donation amounts.

MitigationUpdate GiveWP to version 3.22.2 or later to remediate the improper capability validation; verify that Subscriber-role users can no longer access donation reports after patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GivewpWordPress extension
Affected:< 3.22.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GiveWP plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'GiveWP - Donation Plugin' in the installed plugins list, or inspect the plugin header file at /wp-content/plugins/give/ for the version number in the main plugin file
    Affected if GiveWP plugin is present in the WordPress installation
  2. Identify installed GiveWP version
    Check the plugin version in the WordPress plugin admin page, or open /wp-content/plugins/give/readme.txt and locate the 'Stable tag' entry, or query the WordPress database in wp_options for option_name='give_version'
    Affected if Version is less than 3.22.2
  3. Verify Subscriber role users exist
    Go to WordPress admin > Users > All Users and filter or scroll to identify users with the 'Subscriber' role, or query the wp_usermeta table where meta_key='wp_capabilities' and meta_value contains 'subscriber'
    Affected if At least one user with Subscriber role exists in the WordPress site
  4. Check if donation reports are accessible to low-privilege users
    Log in with a test Subscriber-level account and attempt to access the donation reports page at /wp-admin/admin.php?page=give-reports, or use a browser developer tool to inspect HTTP responses when a Subscriber attempts to access donation data via GiveWP API endpoints
    Affected if Subscriber-level users can view, retrieve, or export donation reports containing donor names and amounts without receiving an authorization error

A user is affected if GiveWP version is below 3.22.2 and Subscriber-role users can access donation reports that should require higher privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.22.2 or later
Fixed in 3.22.2
Interim mitigation

Update GiveWP to version 3.22.2 or later to remediate the improper capability validation; verify that Subscriber-role users can no longer access donation reports after patching.

Recommended fix High confidence

GiveWP version 3.22.2

  1. 1. Create a full backup of your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the GiveWP plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 3.22.2 or later
  5. 5. After updating, verify the plugin version shows 3.22.2 or higher under the plugin name
  6. 6. Test that donation forms and donor management functionality still work correctly
Caveat Check the GiveWP changelog for any breaking changes between your current version and 3.22.2 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Givewp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2331 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data