CVE-2026-8206
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 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.
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 · high confidenceThe Kirki WordPress plugin versions 6.0.0-6.0.6 fails to validate that the email address matches the username during password reset requests, allowing unauthenticated attackers to hijack the reset token by specifying their own email address while providing any valid username. This grants attackers a password reset link for the target user, enabling full account takeover.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Kirki plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Kirki Customizer Framework' in the list. Alternatively, check the /wp-content/plugins/kirki/ directory exists on the server.Affected if The Kirki plugin is present in the WordPress installation
-
Identify installed Kirki versionIn WordPress admin > Plugins > Installed Plugins, find Kirki and view the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/kirki/ for the 'Version' comment.Affected if The version number is 6.0.0 through 6.0.6 inclusive
-
Verify password reset endpoint accessibilityAttempt to access the WordPress password reset page at /wp-login.php?action=rp or test the wpLostPassword endpoint. The vulnerability allows unauthenticated users to request a reset for any username.Affected if The password reset form is accessible without authentication and accepts a username parameter
-
Confirm WordPress user accounts existCheck if there are user accounts configured in WordPress (Users > All Users). The attack requires a valid username to target.Affected if There is at least one user account with a known username in the WordPress installation
A WordPress site is affected if the Kirki plugin versions 6.0.0-6.0.6 are installed and active, and the password reset functionality is publicly accessible to unauthenticated users.
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 where this vulnerability is patched. If unable to update immediately, consider disabling the plugin or implementing additional server-side validation on password reset requests.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8206 — 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-8206 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