Information Disclosure in GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin) (CVE-2025-8620)
Summary
Vulnerability in GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin) (CVE-2025-8620). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 4.6.0. This makes it possible for unauthenticated attackers to extract donor names, emails, and donor id. CVE-2025-47444 is a duplicate of this issue. CVE-2025-47444 is a duplicate of this issue.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-8620 has been found in GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin).
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin) CVE-2025-8620" on the vendor's site.
CVE-2025-8620 (GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin)) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin).
Check the vendor advisory for the affected versions of GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin).
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで GiveWP – Donation Plugin and Fundraising Platform (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory nvd.nist.gov
- report github.com
- web plugins.trac.wordpress.org
- web linkedin.com
- web wordfence.com