CVE-2026-104734

7.2High

Published 17 Oct 2026 · NVD status: Received · AI triage by gemini-3.8-flash

7.2High

Attack vector: Network
Complexity: Low
Privileges needed: High
User interaction: None
Impact: Full C/I/A compromise
Weakness: CWE-502

Impact

Authenticated attackers with Editor-level access or above can execute arbitrary code, delete files, or read sensitive data if another installed plugin or theme provides a POP chain. Attackers need network access and valid credentials with at least Editor privileges to hit the plugin's import endpoint.

Root cause

The template import functionality deserializes untrusted user input directly without adequate validation.

Affected systems

Kirki Customizer Framework plugin for WordPress versions up to and including 6.3.2

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Fix & remediation

Upgrade Kirki to a version higher than 6.3.2. As an interim workaround, restrict or disable Editor access to the import endpoint or disable the Kirki plugin entirely if an update cannot be deployed immediately.

shell

$ wp plugin update kirki

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

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 FULL_ACCESS to the plugin's import endpoint via the KIRKI_USERS_DEFAULT_FULL_ACCESS configuration, meaning exploitation is possible at Editor privilege level rather than being restricted to administrators alone.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-104734