Strategic Overview
- Status
- Patched in 1.9.5.6
- Affected Plugin
- Participants Database
- Affected Version
< 1.9.5.6- CVSS
- 7.5High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2020-8596
At a glance
CVE-2020-8596 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Participants Database WordPress plugin, affecting versions < 1.9.5.6. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). The issue is fixed in version 1.9.5.6; sites on affected versions should update now. Disclosed February 2020, reported by Teacish.
Vulnerability Overview
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).
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in Participants Database < 1.9.5.6 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Participants Database the fix is 1.9.5.6: builds < 1.9.5.6 are affected, anything from 1.9.5.6 onward is not.
Remediation
Update to version 1.9.5.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Participants Database: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Participants Database 1.9.5.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Participants Database
- 9.1CVE-2026-28189: Participants Database Arbitrary File Deletion
CVE-2026-28189 - 9.1CVE-2026-59555: Participants Database Arbitrary File Deletion
CVE-2026-59555 - 8.1CVE-2024-43141: Participants Database <= 2.5.9.2 PHP Object Injection
CVE-2024-43141 - 6.4CVE-2025-58008: Participants Database <= 2.7.6.3 Stored XSS
CVE-2025-58008 - 6.1CVE-2017-14126: Participants Database <= 1.7.5.9 Unauthorized XSS
CVE-2017-14126 - 5.4CVE-2023-31235: Participants Database <= 2.4.9 CSRF
CVE-2023-31235 - 5.3CVE-2026-11354: Participants Database Unauthenticated Arbitrary
CVE-2026-11354 - 5.3CVE-2023-48751: Participants Database <= 2.5.5 Missing Authorization
CVE-2023-48751
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C