CVE-2026-8096 MEDIUM

CVE-2026-8096: Kirki <= 6.0.6 - Missing Authorization to Authenticated (Subscriber+) Sensitive Form Submission Data Exposure via 'kirki_wp_admin_get_apis' Action

Vendor Themeum
Product Kirki – Freeform Page Builder, Website Builder & Customizer
Weakness CWE-862 · Missing authorization
Published May 19, 2026
Last update May 19, 2026

CVSS base score

6.5/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity None

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Kirki Page Builder versions up to 6.0.6 lack proper authorization checks, allowing authenticated users with low privileges to read sensitive data they should not access. An attacker with a basic user account can retrieve confidential information through the plugin's API or admin functions without additional restrictions. Update to a version newer than 6.0.6 to resolve this issue.

What an attacker can do

03Attacker Capabilities

Read sensitive data and configuration information they should not have access to.

Potential impact on your site

04Site Impact

User data, site configuration, or other confidential information may be exposed to low-privilege users.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

May 19, 2026 CVE published
May 19, 2026 Record updated

Related vulnerabilities

08Related CVE