CVE-2026-82568 · Package
NO FIX YET · SEE WHAT TO DO
The Give Peer-to-Peer WordPress plugin lets unauthenticated visitors inject SQL through the 'sort' parameter, in all versions up to and including 2.9.3. An attacker can read sensitive data from the site's database, and the sources say it can be chained with CVE-2026-82663 to reach remote code execution.
first public Nov 15, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the Give Peer-to-Peer plugin at version 2.9.3 or earlier that have at least one Peer-to-Peer campaign. The sources do not say whether the flaw is reachable on sites without a campaign, and the sources do not describe a configuration that avoids it beyond that. Sites without this plugin are not affected.
Not affected if plugin-above-2.9.3, plugin-not-installed
Who cares give, self-hosted, wordpress
wp-content/plugins/2.9.3; the sources do not name the exact fixed versionThe Give - Peer-to-Peer plugin for WordPress is vulnerable to time-based SQL Injection via the 'sort' parameter in all versions up to, and including, 2.9.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Successful exploitation requires the existence of at least one Peer-to-Peer campaign. This vulnerability can be combined with CVE-2026-82663 to achieve unauthenticated remote code execution.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.