CVE-2026-84221: Kirki 6.0.0 - 6.2.5 - Editor+ SQLi via Content Manager Field ID
The Kirki WordPress plugin before 6.3.0 does not escape a user-supplied identifier before using it in a SQL query, allowing users with editor-level access and above to append arbitrary SQL and read the contents of the database, including user credentials.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated WordPress user with editor-level access or higher can exploit it. Sites where editor accounts are limited to trusted users have a narrower exposure than sites that grant editor access to less-trusted contributors.
What access does an attacker need?
The attacker needs an account with at least the Editor role and must be able to provide a crafted identifier through the Content Manager field. The issue is not described as exploitable by unauthenticated visitors or lower-privileged users.
What data could be exposed?
An attacker can append arbitrary SQL and read database contents. This may include user credentials, according to the advisory.
Which versions need remediation?
Kirki versions 6.0.0 through 6.2.5 are affected, and the issue is fixed in version 6.3.0. Upgrade to 6.3.0 or later.