Kirki exposes an unauthenticated SQL-injection path
Kirki before 6.0.13 places an unauthenticated request value into a SQL statement without sufficient sanitization or escaping. An attacker can alter the generated database query and use the SQL-injection primitive to infer or read data available to the WordPress database account. The published.
- Component
- Kirki
- Plugin slug
kirki- Affected
- < 6.0.13
- Safe version
6.0.13- Published
- Jul 31, 2026
This CVE was published Jul 31, 2026 and is one of 42 known issues for this plugin.
Update, patch or deactivate.
Update Kirki to 6.0.13 or later. Review web and database logs for unusual Kirki-related requests containing SQL syntax or time-delay probes, and rotate credentials or secrets if database disclosure is suspected. If the update cannot be applied promptly, deactivate the affected functionality or plugin when the site's risk profile warrants it.
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 Kirki WordPress plugin before 6.0.13 does not properly sanitise and escape a value taken from the request before using it in a SQL statement, allowing unauthenticated attackers to perform SQL injection attacks.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N