Participants Database
participants-database · plugin
Known security vulnerabilities for Participants Database. Find out in seconds which version runs on your site with WP Lens.
16 known vulnerabilities
6 critical · 11 exploitable without logging in · 2 with public exploit code · latest Oct 23, 2026
Before you install
Do not install
- Closed on wordpress.org on Oct 19, 2026; no updates will come.
- 7 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Closed on wordpress.org
Removed from the directory on Oct 19, 2026 · reason: no reason given. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Nov 13, 2026
Vulnerabilities
- Critical 10.0
CVE-2026-59555unauthenticated≤ 2.7.8.3
WordPress Participants Database plugin <= 2.7.8.3 - Arbitrary File Deletion vulnerability
- Critical 9.8
CVE-2026-112862unauthenticated≤ 2.7.8.5
WordPress Participants Database plugin <= 2.7.8.5 - PHP Object Injection vulnerability
- Critical 9.8
CVE-2024-43141unauthenticated≤ 2.5.9.2
WordPress Participants Database plugin <= 2.5.9.2 - PHP Object Injection vulnerability
- Critical 9.3
CVE-2026-112860unauthenticated≤ 2.7.8.5
WordPress Participants Database plugin <= 2.7.8.5 - SQL Injection vulnerability
- Critical 9.3
CVE-2026-59525unauthenticated≤ 2.7.8.3
WordPress Participants Database plugin <= 2.7.8.3 - SQL Injection vulnerability
- Critical 9.1
CVE-2026-13596unauthenticated→ 2.7.8.4
Participants Database < 2.7.8.4 - Unauthenticated SQL Injection via List Search
- High 8.8
CVE-2023-31235unauthenticated · needs a click≤ 2.4.9
WordPress Participants Database Plugin <= 2.4.9 is vulnerable to Cross Site Request Forgery (CSRF)
- High 8.8
CVE-2023-48751login required≤ 2.5.5
WordPress Participants Database Plugin <= 2.5.5 is vulnerable to Broken Access Control
- High 7.5
SQL injection vulnerability in the Export CSV page in the Participants Database plugin before 1.5.4.9 for WordPress allows remote attackers
- High 7.4
CVE-2026-28189unauthenticated · needs a click≤ 2.7.8.4
WordPress Participants Database plugin <= 2.7.8.4 - Arbitrary File Deletion vulnerability
- Medium 6.5
CVE-2025-58008login required≤ 2.7.6.3
WordPress Participants Database Plugin <= 2.7.6.3 - Cross Site Scripting (XSS) Vulnerability
- Medium 6.3
CVE-2026-112861login required≤ 2.7.8.5
WordPress Participants Database plugin <= 2.7.8.5 - Insecure Direct Object References (IDOR) vulnerability
- Medium 6.1
CVE-2017-14126unauthenticated · needs a click
The Participants Database plugin before 1.7.5.10 for WordPress has XSS.
- Medium 5.3
CVE-2026-11354unauthenticated≤ 2.7.8.3
Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter
- Medium 4.3
CVE-2022-47612unauthenticated · needs a click≤ 2.4.5
WordPress Participants Database Plugin <= 2.4.5 is vulnerable to Cross Site Request Forgery (CSRF)
- Medium 4.3
CVE-2026-27423subscriber+≤ 2.7.8.4
WordPress Participants Database plugin <= 2.7.8.4 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.