CVE-2026-84221
Received Received - Intake

Stored SQL Injection in Kirki WordPress Plugin

Publication date: 2026-09-05

Last updated on: 2026-09-06

Assigner: WPScan

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-05
Last Modified
2026-09-06
Generated
2026-09-25
AI Q&A
2026-09-05
EPSS Evaluated
2026-09-24
NVD
CVE-2026-84221
EUVD
EUVD-2026-71862

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
aristath kirki to 6.3.0 (exc)
kirki plugin to 6.3.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a SQL injection flaw in the Kirki WordPress plugin versions 6.0.0 to 6.2.5. It occurs because the plugin does not properly escape user-supplied input before using it in SQL queries. This allows users with editor-level access or higher to inject malicious SQL code and read sensitive database contents, including user credentials.

Detection Guidance

To detect this vulnerability, check the installed version of the Kirki WordPress plugin. If it is between 6.0.0 and 6.2.5, the system is vulnerable. You can verify the version via WordPress admin panel or by inspecting the plugin files on the server.

Impact Analysis

If you use the vulnerable Kirki plugin versions, attackers with editor-level access or higher could exploit this flaw to read your database contents, including sensitive information like user credentials. This could lead to unauthorized access to user accounts and potential data breaches.

Compliance Impact

This vulnerability could lead to unauthorized access to personal data, violating GDPR and HIPAA requirements for data protection and security. Organizations may face legal penalties, reputational damage, and loss of trust due to non-compliance with these regulations.

Mitigation Strategies

Immediately update the Kirki plugin to version 6.3.0 or later. Remove editor-level or higher user access if not required. Monitor database access logs for unusual SQL queries or unauthorized data reads.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-84221. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart