HomeWordPress vulnerabilitiesParticipants Database
Participants Database vulnerabilities
Participants Database has 5 known vulnerabilities in this database. The most recent published record is dated 1 Aug 2026.
- Known vulnerabilities
- 5
- Active installs
- 7,000+
- Latest version
- 2.7.8.5
- Last updated
- 31 Jul 2026
- Most recent
- 1 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-13596 | Critical 9.1 | Before 2.7.8.4 | Fixed in 2.7.8.4 | 1 Aug 2026 |
| Sensitive data exposure CVE-2026-11354 | Medium 5.3 | Up to 2.7.8.3 | Fixed in a later version (latest 2.7.8.5) | 24 Jul 2026 |
| SQL injection CVE-2020-8596 | High 7.5 | Up to 1.9.5.5 | Fixed in a later version (latest 2.7.8.5) | 11 Feb 2020 |
| Cross-site scripting (XSS) CVE-2017-14126 | Medium 6.1 | Before 1.7.5.10 | Fixed in 1.7.5.10 | 4 Sep 2017 |
| SQL injection CVE-2014-3961 | Not scored | Up to 1.5.4.8 | Fixed in a later version (latest 2.7.8.5) | 4 Jun 2014 |
Read the published descriptions
- CVE-2026-13596, 1 Aug 2026
- The Participants Database WordPress plugin before 2.7.8.4 does not properly sanitize and escape a user-supplied parameter before using it in a SQL query, allowing unauthenticated attackers to perform SQL injection attacks. CVE record
- CVE-2026-11354, 24 Jul 2026
- The Participants Database plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.7.8.3 via the 'id' parameter. This makes it possible for unauthenticated attackers to overwrite arbitrary participant records by numeric ID and redirect the private_id-bearing record-access link to an attacker-controlled email address, granting full read and edit access to the victim's stored personally identifiable information including names, email addresses, phone numbers, and any other fields collected in the participant database. An attacker can harvest a valid nonce with a plain unauthenticated GET request to any page rendering the public signup or record form, then POST action=update with an arbitrary id value to overwrite any record; chaining a subsequent action=retrieve then delivers the private-access link to the attacker-controlled mailbox. CVE record
- CVE-2020-8596, 11 Feb 2020
- participants-database.php in the Participants Database plugin 1.9.5.5 and previous versions for WordPress has a time-based SQL injection vulnerability via the ascdesc, list_filter_count, or sortBy parameters. It is possible to exfiltrate data and potentially execute code (if certain conditions are met). CVE record
- CVE-2017-14126, 4 Sep 2017
- The Participants Database plugin before 1.7.5.10 for WordPress has XSS. CVE record
- CVE-2014-3961, 4 Jun 2014
- SQL injection vulnerability in the Export CSV page in the Participants Database plugin before 1.5.4.9 for WordPress allows remote attackers to execute arbitrary SQL commands via the query parameter in an "output CSV" action to pdb-signup/. CVE record
What to do if you run Participants Database
If you run Participants Database, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Participants Database vulnerabilities
Free. We email you when a new vulnerability is published for Participants Database, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.