CVE-2026-102291: Kirki – Freeform Page Builder, Website Builder & Customizer <= 6.3.1 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via 'display_name'
The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 6.3.1 This is due to the plugin substituting a user's displayname into the composed page markup unfiltered and then running the whole result through doshortcode() in TheFrontend::replacecontent(). Because displayname is writable by any user on their own account through the core profile form, this makes it possible for authenticated attackers with Subscriber-level access and above to execute arbitrary shortcodes. Where the page is a users collection — an ordinary team or member-directory page — the shortcode runs in the request of every visitor, including unauthenticated ones. Requires a published page with a Kirki element whose dynamic content is bound to the displayname user field.
Affected Software
Event History
Frequently Asked Questions
Which sites are exposed to this issue?
Exposure requires a published page containing a Kirki element with dynamic content bound to the user display_name field. The affected page must be a users collection, such as a team or member-directory page.
What access does an attacker need?
An attacker needs an authenticated WordPress account with Subscriber-level access or higher. They can modify their own display name through the standard WordPress profile form.
Are all installations affected by default?
No. Exploitation depends on the presence of the specific published Kirki page configuration that renders users and binds dynamic content to display_name.
What is the impact if an affected page is visited?
The attacker-controlled shortcode is executed when the affected users collection page is requested. This can occur for every visitor to that page, including unauthenticated visitors.
How can administrators identify potentially affected pages?
Review published Kirki pages for users-collection elements, especially team or member-directory pages, and check whether their dynamic content uses the display_name user field. Review user display names for shortcode-like content on sites with that configuration.