Give - Peer-to-Peer <= 2.9.5 - Authorization Bypass to Team Modification and Media Upload
Strategic Overview
- Status
- Patched in 2.9.6
- Affected Plugin
- Give - Peer-to-Peer
- Affected Version
<= 2.9.5- CVSS
- 7.5High
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-82663
At a glance
CVE-2026-82663 is a high-severity Incorrect Authorization vulnerability in the Give - Peer-to-Peer WordPress plugin, affecting versions <= 2.9.5. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.9.6; sites on affected versions should update now. Disclosed November 2026, reported by Alex Thomas.
Vulnerability Overview
The Give - Peer-to-Peer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.9.5. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers who know or discover an existing campaign and team ID to modify the team's name, story, goal, access and notification settings, set its profile image URL, and upload WordPress-allowed media files as parentless attachments. This vulnerability can be combined with CVE-2026-82568 to achieve unauthenticated remote code execution.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-863: Incorrect Authorization
Reaching this weakness in Give - Peer-to-Peer <= 2.9.5 takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Give - Peer-to-Peer the fix is 2.9.6: builds <= 2.9.5 are affected, anything from 2.9.6 onward is not.
Remediation
Update to version 2.9.6, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Give - Peer-to-Peer 2.9.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Give - Peer-to-Peer
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C