dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-57726

CRITICAL · 9.3 CVSS v3.1 Published 2026-07-13
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 5 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themeum Kirki kirki allows Blind SQL Injection.This issue affects Kirki: from n/a through <= 6.0.12.

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

Blind SQL Injection vulnerability in Themeum Kirki WordPress plugin (versions through <=6.0.12) allows remote attackers to inject malicious SQL commands via improper neutralization of special elements in database queries. The 'blind' classification indicates attackers infer database information through behavioral differences rather than direct output, which is equally dangerous but requires more sophisticated exploitation.

MitigationUpdate Kirki plugin to latest version immediately; if no patch available, disable the plugin until remediation. Apply parameterized queries or prepared statements to fix the vulnerable code path.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 Kirki plugin installation and version
    Navigate to WordPress admin > Plugins and locate Themeum Kirki (or Kirki Customizer Framework). Note the installed version number. Alternatively, check the plugin header in wp-content/plugins/kirki/ directory or use a plugin audit tool.
    Affected if Kirki plugin is installed and version is 6.0.12 or earlier (any version 'through 6.0.12' as stated)
  2. Identify exposed input parameters
    Review the plugin code for any $_GET, $_POST, or $_REQUEST usage that feeds directly into SQL queries without prepare() or esc_sql() functions. Focus on endpoints that handle user-supplied data accessible without authentication.
    Affected if Unsanitized input parameters exist in the plugin and are reachable by unauthenticated users
  3. Inspect web server access logs
    Search access logs (Apache/Nginx) for requests to wp-admin/admin-ajax.php or other Kirki-related endpoints containing SQL metacharacters such as quotes, UNION, SLEEP, or boolean operators (AND, OR) in query parameters.
    Affected if Log entries show SQL injection probe patterns targeting Kirki endpoints from external IPs
  4. Check for unauthorized database modifications
    Query the WordPress database (wp_options table or custom tables) for unexpected or suspicious entries that may indicate successful SQL injection, such as new admin users or modified settings.
    Affected if Unexpected database records exist that were not created by legitimate administrators
  5. Verify unauthenticated access to vulnerable endpoints
    Test if affected Kirki AJAX actions or form handlers are accessible without authentication by sending requests with SQL injection payloads (e.g., parameter=1' AND SLEEP(5)--) and measuring response time.
    Affected if The affected endpoints accept unauthenticated requests and respond to injected SQL syntax

If the Kirki plugin is installed at version 6.0.12 or earlier and its input-handling endpoints are exposed to unauthenticated users, the environment is vulnerable to blind 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Kirki plugin to latest version immediately; if no patch available, disable the plugin until remediation. Apply parameterized queries or prepared statements to fix the vulnerable code path.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57726 — 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-57726 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