CVE-2026-102291 json
Kirki – Freeform Page Builder, Website Builder & Customizer <= 6.3.1 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via 'display_name'
published 30d ago modified 27d ago also EUVD-2026-96287
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
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 `display_name` into the composed page markup unfiltered and then running the whole result through `do_shortcode()` in `TheFrontend::replace_content()`. Because `display_name` 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 `display_name` user field.
Is CVE-2026-102291 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 29d ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected products
- themeum Kirki – Freeform Page Builder, Website Builder & Customizer
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/bed93040-a843-417e-89b4-5ab3cba788aa?source=cve
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.1/includes/Frontend/TheFrontend.php#L144
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.1/includes/Frontend/Preview/Utils.php#L408
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.1/includes/Frontend/Preview/Utils.php#L308
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.1/includes/Frontend/Preview/Utils.php#L334
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.1/includes/HelperFunctions.php#L1117
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.1/includes/Manager/PluginShortcode.php#L40
- plugins.trac.wordpress.org /changeset?reponame=&new=3718900%40kirki%2Ftags%2F6.3.2&old=3697265%40kirki%2Ftags%2F6.3.1
Sources
- CVE List CVE-2026-102291
- NVD CVE-2026-102291
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.