# CVE-2026-13596: Participants Database < 2.7.8.4 - Unauthenticated SQL Injection via List Search

> Unauthenticated attackers can execute SQL injection attacks via the list search feature in the Participants Database WordPress plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-xv54-r3hg-rvqj

## What is CVE-2026-13596?

CVE-2026-13596 is a critical SQL injection vulnerability in Unknown Participants Database, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-13596?


## How do I fix CVE-2026-13596?

No fix has been published for CVE-2026-13596 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13596 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13596 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13596 and fix it if it is affected.

What it is: CVE-2026-13596 is a critical SQL injection vulnerability in Unknown Participants Database, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13596 exists.

Affected product: Unknown Participants Database. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13596/ (Markdown: https://insights.sbomify.com/CVE-2026-13596/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13596
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13596
- OSV: https://osv.dev/vulnerability/CVE-2026-13596

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13596/
Summaries are generated and may contain mistakes; the official description above is the record.