CVE-2026-8096
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Kirki WordPress plugin fails to properly verify user authorization before allowing access to view frontend forms and read stored form submission data. This authorization bypass allows authenticated users with subscriber-level permissions to access sensitive visitor information including contact details, messages, and other form submissions that should be restricted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Kirki plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate Kirki. Alternatively, check the main plugin file (kirki.php) header for Version: or use WP-CLI: wp plugin list --name=kirki --format=jsonAffected if Version is lower than 6.0.6 (e.g., 6.0.5, 6.0.0, or any version below 6.0.6)
-
Verify user registration is enabledIn WordPress admin, go to Settings > General and check "Anyone can register" option, or query the site via WP-CLI: wp option get users_can_registerAffected if User registration is enabled, allowing new subscriber-level accounts to be created
-
Identify users with subscriber-level or higher rolesIn WordPress admin, go to Users > All Users and review the role column. Alternatively, use WP-CLI: wp user list --role=subscriber --format=count and repeat for contributor, author, editor, administratorAffected if At least one user account exists with subscriber, contributor, author, editor, or administrator role
-
Confirm form data storage existsCheck the WordPress database for any tables related to Kirki forms, or inspect the frontend for any form shortcodes or blocks from Kirki. Review wp_posts for post_type=kirki_form or similar custom post typesAffected if Kirki forms have been created and may contain visitor submissions with contact details or messages
The environment is affected if Kirki plugin version is below 6.0.6 AND at least one user with subscriber-level or higher access exists, allowing unauthorized access to stored form submissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Kirki plugin to version 6.0.7 or later which contains proper authorization checks to verify user permissions before allowing access to form data.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data