Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesKirki

Kirki vulnerabilities

Kirki has 28 known vulnerabilities in this database. The most recent published record is dated 7 Oct 2026.

Known vulnerabilities
28
Active installs
500,000+
Latest version
6.3.2
Last updated
29 Sep 2026
Most recent
7 Oct 2026

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Cross-site scripting (XSS)
CVE-2026-102173
High 7.2Up to 6.3.1Fixed in a later version (latest 6.3.2)18 h ago
Security weakness
CVE-2026-103065
High 8.2Up to 6.3.1Fixed in a later version (latest 6.3.2)4 d ago
Server-side request forgery (SSRF)
CVE-2026-18335
Medium 5.4Up to 6.2.0Fixed in a later version (latest 6.3.2)13 d ago
Cross-site scripting (XSS)
CVE-2026-84223
Medium 6.8Before 6.3.1Fixed in 6.3.120 Sep 2026
Cross-site scripting (XSS)
CVE-2026-17037
High 7.2Up to 6.2.0Fixed in a later version (latest 6.3.2)11 Sep 2026
Sensitive data exposure
CVE-2026-84222
Medium 5.3Before 6.3.0Fixed in 6.3.09 Sep 2026
Cross-site scripting (XSS)
CVE-2026-84219
High 7.5Before 6.3.0Fixed in 6.3.06 Sep 2026
SQL injection
CVE-2026-84221
Medium 6.8Before 6.3.0Fixed in 6.3.05 Sep 2026
Broken access control
CVE-2026-84225
Low 2.2Before 6.3.0Fixed in 6.3.05 Sep 2026
Sensitive data exposure
CVE-2026-77754
Medium 5.3Before 6.0.14Fixed in 6.0.1426 Aug 2026
Cross-site scripting (XSS)
CVE-2026-74992
Medium 6.8Before 6.2.3Fixed in 6.2.320 Aug 2026
Path traversal
CVE-2026-17604
Medium 4.9Up to 6.1.1Fixed in a later version (latest 6.3.2)16 Aug 2026
Broken access control
CVE-2026-18347
Medium 4.3Up to 6.1.1Fixed in a later version (latest 6.3.2)16 Aug 2026
Security weakness
CVE-2026-16747
Medium 6.5Before 6.2.1Fixed in 6.2.112 Aug 2026
Cross-site scripting (XSS)
CVE-2026-16974
Medium 6.4Up to 6.2.0Fixed in a later version (latest 6.3.2)11 Aug 2026
Remote code execution
CVE-2026-15601
Medium 4.9Up to 6.0.13Fixed in a later version (latest 6.3.2)1 Aug 2026
SQL injection
CVE-2026-12721
High 8.6Before 6.0.13Fixed in 6.0.1331 Jul 2026
Remote code execution
CVE-2026-12720
High 7.5Before 6.0.13Fixed in 6.0.1331 Jul 2026
Broken access control
CVE-2026-13464
Medium 5.3Up to 6.0.14Fixed in a later version (latest 6.3.2)24 Jul 2026
Server-side request forgery (SSRF)
CVE-2026-13147
Critical 9.1Before 6.0.12Fixed in 6.0.1220 Jul 2026
Broken access control
CVE-2026-12723
Medium 5.3Before 6.0.12Fixed in 6.0.1220 Jul 2026
Security weakness
CVE-2026-12724
Medium 4.3Before 6.0.12Fixed in 6.0.1220 Jul 2026
Path traversal
CVE-2026-15457
Medium 4.9Up to 6.0.13Fixed in a later version (latest 6.3.2)17 Jul 2026
Sensitive data exposure
CVE-2026-12122
Medium 5.3Up to 6.0.11Fixed in a later version (latest 6.3.2)2 Jul 2026
Broken access control
CVE-2026-12472
Medium 5.3Up to 6.0.11Fixed in a later version (latest 6.3.2)2 Jul 2026
Privilege escalation
CVE-2026-8206
Critical 9.8Not yet publishedCheck for an update2 Jun 2026
Arbitrary file deletion
CVE-2026-8073
High 7.5Up to 6.0.6Fixed in a later version (latest 6.3.2)19 May 2026
Broken access control
CVE-2026-8096
Medium 6.5Up to 6.0.6Fixed in a later version (latest 6.3.2)19 May 2026
Read the published descriptions
CVE-2026-102173, 7 Oct 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via registration metadata in all versions up to, and including, 6.3.1 This is due to insufficient escaping in `ExceptionalElements::image_element()`, which concatenates a user-meta value straight into an `<img src="…">` attribute. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute whenever a user accesses a page rendering a Kirki users collection whose image element is bound to one of the nine registration meta fields. Requires public user registration to be enabled and a published page carrying a `kirki-register` element, which prints the required element nonce into the public markup. CVE record
CVE-2026-103065, 3 Oct 2026
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1. CVE record
CVE-2026-18335, 24 Sep 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 6.2.0 via the 'kirki_data' Parameter. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. CVE record
CVE-2026-84223, 20 Sep 2026
The Kirki WordPress plugin before 6.3.1 does not sanitize uploaded SVG files while making them uploadable site-wide, allowing users with author-level access and above to upload a file containing JavaScript which is then served from the site's own origin and runs in the session of anyone who opens it. CVE record
CVE-2026-17037, 11 Sep 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘comment’ parameter in all versions up to, and including, 6.2.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2026-84222, 9 Sep 2026
The Kirki WordPress plugin before 6.3.0 does not check whether the requester is allowed to read a post before rendering and returning its page content, allowing unauthenticated users to retrieve the content of pages that are not publicly available, such as private, draft, pending and trashed ones. CVE record
CVE-2026-84219, 6 Sep 2026
The Kirki WordPress plugin before 6.3.0 does not hold back every spelling of the HTML entities it decodes when rendering, allowing unauthenticated users to store JavaScript in a comment which then runs in the session of anyone viewing a page that displays it, including an administrator, and on every page of the site when its header or footer is built to show comments. CVE record
CVE-2026-84221, 5 Sep 2026
The Kirki WordPress plugin before 6.3.0 does not escape a user-supplied identifier before using it in a SQL query, allowing users with editor-level access and above to append arbitrary SQL and read the contents of the database, including user credentials. CVE record
CVE-2026-84225, 5 Sep 2026
The Kirki WordPress plugin before 6.3.0 does not check that a user is allowed to act on a collaboration comment before changing its state, allowing users whom an administrator has granted content-level access to the page builder to modify comments left by other users, including on pages they cannot themselves open. CVE record
CVE-2026-77754, 26 Aug 2026
The Kirki WordPress plugin before 6.0.14 does not perform a capability check on some endpoints of one of its public AJAX actions, allowing unauthenticated users to retrieve the email addresses of registered users and comment authors, as well as non-public page content and settings. CVE record
CVE-2026-74992, 20 Aug 2026
The Kirki WordPress plugin before 6.2.3 does not properly validate the files contained in archives uploaded by users with the Editor role, and does not remove all unwanted files after extracting them, allowing such users to upload arbitrary files to a web accessible directory, leading to Stored XSS as well as RCE on some server configurations. CVE record
CVE-2026-17604, 16 Aug 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 6.1.1 via the 'data' parameter parameter. This makes it possible for authenticated attackers, with editor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. The intended strpos()-based guard against leaving the uploads directory is bypassed by crafting a URL that includes the uploads base path as a substring while embedding directory traversal sequences, such as /wp-content/uploads/../../wp-config.php. CVE record
CVE-2026-18347, 16 Aug 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.1.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to read arbitrary user metadata and sensitive user record fields - including email address, assigned roles, registration date, and any user_meta values - belonging to any WordPress user including administrators, by supplying a target user ID with a user-type context to the frontend collection endpoint. CVE record
CVE-2026-16747, 12 Aug 2026
The Kirki WordPress plugin before 6.2.1 does not properly authorise its front-end form submission REST routes and passes attacker-controlled input through shortcode execution, allowing unauthenticated users to run any shortcode registered on the site, which on a default install leads to disclosure of the site administrator's email address and an arbitrary-recipient mail relay from the victim's domain. CVE record
CVE-2026-16974, 11 Aug 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the post_meta Shortcode in all versions up to, and including, 6.2.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2026-15601, 1 Aug 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Path Traversal (Zip Slip) in all versions up to, and including, 6.0.13 via the extract_zip_file function. This makes it possible for authenticated attackers, with custom-level access and above, to write arbitrary files on the server, which can allow for remote code execution. The install_app, update_app, and get_kirki_template_from_zip code paths accept a user-supplied app src value to construct the download URL, and no sanitization is applied to prevent a crafted ZIP from being fetched and extracted with path-traversing entry names that escape the intended destination directory. CVE record
CVE-2026-12721, 31 Jul 2026
The Kirki WordPress plugin before 6.0.13 does not properly sanitise and escape a value taken from the request before using it in a SQL statement, allowing unauthenticated attackers to perform SQL injection attacks. CVE record
CVE-2026-12720, 31 Jul 2026
The Kirki WordPress plugin before 6.0.13 does not restrict which classes may be instantiated when it deserialises data that unauthenticated users can store, leading to PHP Object Injection that is triggered when an administrator later reviews the stored data. With a suitable gadget chain present on the site (via another installed Kirki WordPress plugin before 6.0.13, , or an outdated WordPress version), this could be leveraged to perform a variety of attacks, such as remote code execution. CVE record
CVE-2026-13464, 24 Jul 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.0.14 via the 'context' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to read the full title, content, and excerpt of any WordPress post - including drafts, pending, privately published, password-protected, and trashed posts - regardless of author, by supplying an arbitrary post ID via the context parameter alongside an attacker-controlled block template. CVE record
CVE-2026-13147, 20 Jul 2026
The Kirki WordPress plugin before 6.0.12 does not validate a user-supplied URL before requesting it server-side, allowing unauthenticated attackers to make the site issue HTTP requests to arbitrary hosts (Server-Side Request Forgery). CVE record
CVE-2026-12723, 20 Jul 2026
The Kirki WordPress plugin before 6.0.12 does not perform any authorisation check on one of its REST routes, allowing unauthenticated users to overwrite the content of arbitrary existing comments and to create pre-approved comments under a spoofed identity, bypassing comment moderation. CVE record
CVE-2026-12724, 20 Jul 2026
The Kirki WordPress plugin before 6.0.12 does not sanitise or escape the email subject and body values supplied in a request before including them in the password-reset email it sends as HTML, allowing unauthenticated users to inject arbitrary HTML into the message delivered to a registered user, which can be used for phishing. CVE record
CVE-2026-15457, 17 Jul 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 6.0.13 via the 'family' parameter. This makes it possible for authenticated attackers, with editor-level access and above, to delete arbitrary directories on the server, which can result in loss of data and availability. CVE record
CVE-2026-12122, 2 Jul 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 6.0.11 via the get_single_symbol. This makes it possible for unauthenticated attackers to extract the full builder metadata and rendered HTML of any kirki_symbol post - including unpublished drafts - by supplying a sequential WordPress post ID. CVE record
CVE-2026-12472, 2 Jul 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.0.11. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to send arbitrary HTML-injected emails - including phishing messages embedding a real, valid WordPress password-reset URL for the targeted user - to any registered user via the site's own mail server, abusing its SPF/DKIM reputation. The attacker-controlled emailSubject parameter is passed to wp_mail() with only sanitize_text_field() applied, while emailBody 'text' items are concatenated raw into the HTML email body with no escaping, and 'chip' items can include the genuine WordPress password-reset link for the targeted account. CVE record
CVE-2026-8206, 2 Jun 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions 6.0.0 to 6.0.6. This is due to the plugin accepting an arbitrary email address when a username is used in the password reset request. This makes it possible for unauthenticated attackers to send a password reset link for any user registered on the site to their own email address. CVE record
CVE-2026-8073, 19 May 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation and missing capability check in the 'downloadZIP' function in all versions up to, and including, 6.0.6. This makes it possible for unauthenticated attackers to read and delete arbitrary files limited in the WordPress uploads base directory. CVE record
CVE-2026-8096, 19 May 2026
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.0.6. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to view all Kirki frontend forms and read stored visitor form submission data, including contact details, messages, and any other visitor-provided information submitted through site forms. CVE record

What to do if you run Kirki

If you run Kirki, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.

If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.

Email me about new Kirki vulnerabilities

Free. We email you when a new vulnerability is published for Kirki, usually within minutes. Confirm by email; unsubscribe any time.

Focus on your business. We’ll take care of your website.

From everyday updates to ongoing care, we keep your website working.

Get website support