Participants Database exposes an unauthenticated SQL-injection path
Participants Database before 2.7.8.4 places an unauthenticated request parameter into a database query without sufficient sanitization or escaping. A visitor can alter the generated SQL and query information available to the WordPress database account. The published record does not disclose the endpoint or action, vulnerable parameter, query-building function, SQL statement or supported extraction technique.
- Component
- Participants Database
- Plugin slug
participants-database- Affected
- < 2.7.8.4
- Safe version
2.7.8.4- Published
- Aug 01, 2026
- Weakness
- Not assigned
This CVE was published Aug 01, 2026 and is one of 12 known issues for this plugin.
Update, patch or deactivate.
Update Participants Database to 2.7.8.4 or later. Review web and database logs for SQL syntax or time-delay probes against plugin requests, rotate credentials and secrets if database disclosure is suspected, and investigate data integrity if injected queries may have modified records.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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.