Kirki archive imports permit Editor arbitrary-file upload
Kirki before 6.2.3 does not adequately validate files inside archives uploaded by an Editor and does not remove every unwanted file after extraction. An Editor can therefore place an arbitrary file in a web-accessible directory. A malicious browser-rendered file can produce stored cross-site scripting, while executable PHP can lead to remote code execution on server configurations that execute PHP from the destination directory.
- Component
- Kirki
- Plugin slug
kirki- Affected
- < 6.2.3
- Safe version
6.2.3- Published
- Aug 20, 2026
This CVE was published Aug 20, 2026 and is one of 42 known issues for this plugin.
Update, patch or deactivate.
Update Kirki to 6.2.3 or later. Review archives imported by Editor-level accounts and inspect the plugin's extraction destination for unexpected files. If executable content may have been reached, treat the site as potentially compromised and rotate affected credentials after investigation.
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.2.3 does not properly validate the files contained in archives uploaded by users with the Editor role, and does not remove all unwanted files after extracting them, allowing such users to upload arbitrary files to a web accessible directory, leading to Stored XSS as well as RCE on some server configurations.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H