CVE-2026-104734: Kirki <= 6.3.2 - Authenticated (Administrator+) PHP Object Injection via Deserialization of Untrusted Input via ZIP Template Import
The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 6.3.2 via deserialization of untrusted input . This makes it possible for authenticated attackers, with administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. By default, Editor-level users are granted FULLACCESS to the plugin's import endpoint via the KIRKIUSERSDEFAULTFULLACCESS configuration, meaning exploitation is possible at Editor privilege level rather than being restricted to administrators alone.
Affected Software
Event History
Frequently Asked Questions
Which users can realistically exploit this issue?
By default, Editor-level users have FULL_ACCESS to the plugin's import endpoint through the KIRKI_USERS_DEFAULT_FULL_ACCESS configuration. This means exploitation is not limited to administrators despite the stated administrator-level requirement.
What additional condition is needed for the object injection to have impact?
The affected software has no known POP chain of its own. A vulnerable site also needs another installed plugin or theme that provides a usable POP chain for the injected object to produce effects such as file deletion, sensitive-data retrieval, or code execution.
What configuration should be reviewed if patching cannot happen immediately?
Review access to Kirki's import endpoint and the KIRKI_USERS_DEFAULT_FULL_ACCESS setting. Restricting Editor-level access to the import functionality reduces exposure while the vulnerable version remains installed.
How can I assess whether the potential impact is greater on my site?
Inventory installed plugins and themes for PHP object POP chains, since the impact depends on one being present outside Kirki. Sites without an additional usable POP chain have no stated impact from this issue.