GivewpWordPress extension
CVE-2025-7205
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 · uneditedThe GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the donor notes parameter in all versions up to, and including, 4.5.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with GiveWP worker-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Additionally, they need to trick an administrator into visiting the legacy version of the site.
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 confidenceThe GiveWP WordPress donation plugin fails to properly sanitize and escape the donor notes parameter, allowing authenticated users with worker-level access to inject malicious JavaScript. This stored XSS executes whenever an administrator accesses pages displaying the injected donor notes.
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
< 4.6.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GiveWP installationIn WordPress admin, go to Plugins > Installed Plugins and locate the GiveWP plugin. Note the version number displayed next to the plugin name.Affected if GiveWP plugin is installed and version is below 4.6.0
-
Confirm plugin version via file inspectionAccess the plugin file directly via FTP or file manager: navigate to /wp-content/plugins/give/readme.txt and check the version in the header section.Affected if Version listed is below 4.6.0 (e.g., 4.5.0, 4.4.x, etc.)
-
Verify donor notes feature accessLog in with a user account that has worker-level access (donor management permissions). Navigate to Donations > Donors and open any donor profile to view the donor notes field.Affected if The donor notes field is accessible and displayed without proper escaping when viewed by an administrator
-
Test for unescaped output in donor notesAs a worker-level user, add a donor note containing a test script tag like <script>alert(1)</script>. Then log in as an administrator and view that donor's profile page.Affected if The script tag executes or renders as raw HTML instead of being escaped
You are affected if GiveWP plugin version is below 4.6.0 and the donor notes feature is in use, as the lack of sanitization on that field allows stored XSS to execute when administrators view donor profiles.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.6.0
Update GiveWP plugin to the latest version beyond 4.5.0 to patch the XSS vulnerability; if immediate update is not possible, implement proper input sanitization and output escaping on all donor note fields.
GiveWP 4.6.0
- Create a full backup of your WordPress site before making any changes
- Update the GiveWP plugin to version 4.6.0 or later through the WordPress admin dashboard (Plugins > Add New > Upload or WordPress updates)
- Verify the update was successfully applied by checking the plugins page and confirming the version number
- Test the donor notes functionality to ensure the XSS fix is working and the application functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Givewp
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7205 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7205 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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