CVE-2026-74992 Kirki CVE debrief

Who should care

Administrators and security teams responsible for WordPress installations using the Kirki plugin, especially those allowing file uploads or with high-risk server configurations, should prioritize updating to version 6.2.3 or later to mitigate potential Stored XSS and RCE vulnerabilities. Additionally, they should review their current server configurations, monitor for suspicious file uploads and web activity, and consider implementing additional security controls, such as web application firewalls.

Technical summary

The Kirki WordPress plugin before version 6.2.3 does not properly validate files in user-uploaded archives and does not remove unwanted files after extraction, allowing users with the Editor role to upload arbitrary files to a web-accessible directory. This could lead to Stored XSS and potentially RCE on certain server configurations. The vulnerability is particularly concerning for organizations using the Kirki plugin, especially those allowing file uploads or with high-risk server configurations.

Defensive priority

Organizations using the Kirki WordPress plugin should prioritize updating to version 6.2.3 or later to mitigate potential Stored XSS and RCE vulnerabilities.

Recommended defensive actions

• Update the Kirki WordPress plugin to version 6.2.3 or later
• Restrict file uploads for users with the Editor role
• Monitor for suspicious file uploads and web activity
• Consider implementing additional security controls, such as web application firewalls
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The Kirki WordPress plugin vulnerability allows users with the Editor role to upload arbitrary files to a web-accessible directory, potentially leading to Stored XSS and RCE on certain server configurations. Evidence is based on limited source detail, and further verification is recommended. The CVE record was published on 2026-08-20T06:17:19.360Z and has not been modified since then. However, defenders should verify the affected scope, server configurations, and potential impact on their systems.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.