StellarWP GiveWP cross-site request forgery in donor account linking
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress has a cross-site request forgery flaw that lets a remote, unauthenticated attacker reassign a donor record to an arbitrary WordPress user, provided they can trick a site administrator into clicking a link. The resulting change in donor-account ownership can also satisfy a precondition for a separately tracked account-takeover flaw, CVE-2026-82675.
Written by a model
Original description
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.16.7.2. This is due to missing nonce validation on the give_render_donor_view() function. This makes it possible for unauthenticated attackers to reassign an arbitrary GiveWP donor record to an arbitrary WordPress user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The resulting association changes donor-account ownership and can satisfy the linked-donor precondition for a separately tracked account-takeover vulnerability (CVE-2026-82675).
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-82676 (GiveWP – Donation Plugin and Fundraising Platform <= 4.16.7.2 - Cross-Site Request Forgery to Donor Account Relinking), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-82676 (entry last updated 2026-11-20):
Affected:
- stellarwp GiveWP – Donation Plugin and Fundraising Platform: through 4.16.7.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-82676 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-82676 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ac9c7a5d-f360-4e7f-8f60-747ad761c3d8?source=cve
- https://plugins.trac.wordpress.org/changeset/3680237/give
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-82676
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-82676"}.Affected versions
- stellarwp GiveWP – Donation Plugin and Fundraising Platformthrough 4.16.7.2
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-82676 |
| Record | NVD · CVE-2026-82676 |
| Other links 2 | |
| Link | wordfence.com · threat-intel/vulnerabilities/id/ac9c7a5d-f360-4e7f-8f60-747ad761c3d8?source=cve |
| Link | plugins.trac.wordpress.org · changeset/3680237/give |
Questions about CVE-2026-82676
Is CVE-2026-82676 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-82676?
GiveWP – Donation Plugin and Fundraising Platform: through 4.16.7.2.
Source: cve.now feed data
Related
- CVE-2025-0912GiveWP – Donation Plugin and Fundraising Platform <= 3.19.4 - Unauthenticated PHP Object Injection
- CVE-2024-12877GiveWP – Donation Plugin and Fundraising Platform <= 3.19.2 - Unauthenticated PHP Object Injection
- CVE-2024-9634GiveWP – Donation Plugin and Fundraising Platform <= 3.16.3 - Unauthenticated PHP Object Injection to Remote Code Execution
- CVE-2026-118193GiveWP <= 4.19.1 - Authenticated (Custom+) Privilege Escalation to 'donor_default_user_role' Parameter
- CVE-2026-82675GiveWP – Donation Plugin and Fundraising Platform <= 4.17.0 - Unauthenticated Donor Account Takeover
- CVE-2025-13206GiveWP - Donation Plugin and Fundraising Platform <= 4.13.0 - Unauthenticated Stored Cross-Site Scripting via 'name'
No corrections so far. Something wrong on this page? Report an error.