Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2025-8620

CVE-2025-8620 - And Fundraising Platform Plugin

CVE-2025-8620

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-8620

MEDIUM CVSS 5.3 Published 2025-08-06 Updated 2025-08-12
AI Risk High (80/100) Active Exploit: Likely Published Exploit: Public exploit references found Priority: P2 Urgent
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected Components 3
Reference Links 4
AI Risk Engine High (80/100)
Exploitability High
Active Exploitation Likely
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2025-08-06 CVE published and first recorded in the threat feed.
  2. 2025-08-12 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 7 days ago

AI enriched 7 days ago (2026-04-09 07:36 UTC)

Technical Summary

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.

Potential Impact

Severity is MEDIUM (CVSS 5.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on published exploit references, remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: published exploit references, remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

References

Scroll to top