dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-13596

CRITICAL · 9.1 CVSS v3.1 Published 2026-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Participants Database WordPress plugin before version 2.7.8.4 contains a SQL injection vulnerability due to improper sanitization and escaping of a user-supplied parameter before its use in a SQL query. Unauthenticated attackers can exploit this to inject malicious SQL commands.

MitigationUpdate the Participants Database plugin to version 2.7.8.4 or later to remediate the SQL injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Participants Database plugin is installed
    Check for the plugin directory at wp-content/plugins/participants-database/ or look for 'Participants Database' in WordPress admin Plugins list
    Affected if Plugin is not present in the WordPress installation
  2. Locate the plugin version number
    Access WordPress admin > Plugins > Participants Database and read the version from the plugin description, or inspect the plugin main PHP file header for 'Version:' tag
    Affected if Cannot determine version - treat as potentially vulnerable
  3. Compare installed version to affected range
    Compare your version number to 2.7.8.4 - any version before 2.7.8.4 (such as 2.7.8.3, 2.7.7.x, etc.) is affected
    Affected if Installed version is less than 2.7.8.4 (for example: 2.7.8.3, 2.7.8, 2.7.7, 2.6.5)
  4. Verify the plugin is active
    Check WordPress admin > Plugins to confirm the plugin status is 'Active'
    Affected if Plugin is activated - the unauthenticated SQL injection is exploitable

If the Participants Database plugin is installed, active, and the version is below 2.7.8.4, the environment is vulnerable to unauthenticated SQL injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Participants Database plugin to version 2.7.8.4 or later to remediate the SQL injection vulnerability.

Recommended fix High confidence

2.7.8.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Participants Database' plugin
  4. Click 'Update now' if an update is available, or manually update to version 2.7.8.4
  5. Verify the updated version is 2.7.8.4 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13596 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13596 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data