CVE-2025-2025

Give <= 3.22.0 - Missing Authorization to Unauthenticated Arbitrary Earning Reports Disclosure via give_reports_earnings Function

2025-03-14 22:39
mikemyers

Strategic Overview

Status
Patched in 3.22.1
Affected Plugin
GiveWP – Donation Plugin and Fundraising Platform
Affected Version
<= 3.22.0
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-2025
View all GiveWP – Donation Plugin and Fundraising Platform vulnerabilities

At a glance

CVE-2025-2025 is a medium-severity Missing Authorization vulnerability in the GiveWP WordPress plugin, affecting versions <= 3.22.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 3.22.1; sites on affected versions should update now. Disclosed March 2025, reported by mikemyers.

Vulnerability Overview

The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the give_reports_earnings() function in all versions up to, and including, 3.22.0. This makes it possible for unauthenticated attackers to disclose sensitive information included within earnings reports.

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-862: Missing Authorization

GiveWP <= 3.22.0 carries this weakness at give_reports_earnings(), and reaching it takes no account at all. 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 GiveWP the fix is 3.22.1: builds <= 3.22.0 are affected, anything from 3.22.1 onward is not.

Remediation

Update to version 3.22.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: GiveWP 3.22.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-2025https://www.wordfence.com/threat-intel/vulnerabilities/id/40595943-121d-4492-a0ed-f2de1bd99fdahttps://nvd.nist.gov/vuln/detail/CVE-2025-2025

Related records

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