Donation-status tampering via missing capability check
Published Aug 21, 2025 · Updated Apr 8, 2026
Improper authorization in GiveWP 4.5.0 and earlier allows remote authenticated users to alter donation statuses over the network. The give_update_payment_status() function changes a stored donation status without checking the caller’s required capability. GiveWP Worker-level access or higher is required, and the operation is absent from the user interface.
Summary
What happened
Improper authorization in GiveWP 4.5.0 and earlier allows remote authenticated users to alter donation statuses over the network. The give_update_payment_status() function changes a stored donation status without checking the caller’s required capability. GiveWP Worker-level access or higher is required, and the operation is absent from the user interface.
The record
- CVE
- CVE-2025-7221
- Published
- Aug 21, 2025
- Updated
- Apr 8, 2026
- Vendor
- Liquid Web
- Product
- GiveWP
- Classifications
- CWE-285, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo