Loading vulnerability…
CVE-2026-8206 is a critical unauthenticated account takeover and privilege escalation vulnerability in the Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress. It affects versions 6.0.0 through 6.0.6 and was introduced with the plugin’s custom frontend account-management REST API. The flaw resides in the forgot-password workflow implemented in the handle_forgot_password() method of the CompLibFormHandler class. When a password reset request is made using a valid username, the vulnerable logic identifies the target account, generates a legitimate WordPress password reset key for that user, but fails to verify that the supplied email address belongs to the same account. As a result, the reset message is sent to an attacker-controlled email address rather than the victim’s registered address. The affected endpoint is exposed without authentication, enabling remote exploitation against arbitrary registered users, including administrators.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
6 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone exploit/lab project for CVE-2026-8206, an unauthenticated account takeover vulnerability in the Kirki Customizer Framework WordPress plugin. The repo contains: (1) documentation in README.md and CVE-2026-8206_Report_EN.md describing the bug, affected versions, attack chain, and remediation; (2) poc.py, a Python proof-of-concept that sends a POST request to the vulnerable Kirki forgot-password REST endpoint with attacker-controlled username, email, subject, and body fields; (3) docker-compose.yml, which provisions a local MariaDB, WordPress, and MailHog environment for testing; and (4) setup.ps1, which downloads vulnerable Kirki v6.0.6, places it into the WordPress plugins directory, and starts the Docker lab. The main exploit capability is password reset email hijacking: the PoC abuses the plugin’s failure to verify that the supplied email belongs to the target username, causing WordPress reset links for arbitrary users (default admin) to be sent to an attacker-controlled address. The PoC does not itself automate the full takeover or RCE chain, but the included documentation explains the likely follow-on steps: use the reset link, change the victim password, log in as admin, upload a malicious plugin, and optionally obtain code execution via a webshell. Because the repository includes a working exploit request and a reproducible lab, it is best classified as an operational PoC rather than a mere advisory or detection script.
Repository contains a single Python exploit script and a README. The main file, CVE-2026-8206.py, is a standalone Python exploit targeting CVE-2026-8206 in the Kirki WordPress plugin. Its workflow is: probe common WordPress/login-related paths for Kirki forgot-password forms, fetch page content, extract a Kirki/WordPress nonce from embedded JavaScript or page source, then abuse the vulnerable Kirki REST password-reset functionality to submit a reset request for an arbitrary username while specifying an attacker-controlled email address. The script also includes user-enumeration support and batch processing of multiple usernames, making it more than a simple detector. Based on the visible code and README, the exploit is intended to achieve unauthenticated account takeover of registered WordPress users. The repository structure is minimal: one operational Python script as the entry point and one documentation file describing the vulnerability, usage examples, options, and mitigation guidance.
This repository is a small standalone exploit repo containing one Python exploit script and a minimal README. The main file, CVE-2026-8206.py, targets CVE-2026-8206, described as an unauthenticated account takeover vulnerability affecting a Kirki plugin/CompLib password-reset workflow on WordPress sites. The exploit is not part of a larger framework. Repository structure is simple: the Python script is the operational component and README.md only labels the CVE. The script uses requests, regex parsing, argparse, and HTML parsing support to automate the attack chain. Based on the visible code, it initializes an HTTP session with a browser-like User-Agent, scans common login/reset/account paths for Kirki fingerprints, extracts a nonce from page source using several regex patterns, enumerates WordPress users, and then attempts exploitation for either a single username or a batch list of usernames. Primary capabilities include: reconnaissance for Kirki-enabled forms, nonce extraction from page content, WordPress user enumeration via /wp-json/wp/v2/users and likely fallback methods, and exploitation of the vulnerable password-reset flow to redirect reset emails to an attacker-controlled address. The script supports verbose logging, batch mode, configurable delays, and a dedicated enumeration mode. This makes it more than a detector: it is an operational exploit automation tool intended to produce account takeover conditions. Fingerprintable targets/endpoints in the code include common WordPress/Kirki page paths such as /login/, /register/, /forgot-password/, /password-reset/, /account/, /login-page/, and /wp-login.php, plus the WordPress REST API endpoint /wp-json/wp/v2/users. The code also searches for KirkiComponentLibrary and X-WP-Element-Nonce-related nonce material in page content. The exploit description explicitly references the vulnerable CompLibFormHandler REST API endpoint, although the exact request path is not visible in the provided truncated content. Overall, this is a focused web exploit PoC/operational script for unauthenticated takeover of WordPress accounts on vulnerable Kirki-integrated sites by abusing password reset email redirection.
This repository is a local Docker lab and proof-of-concept for CVE-2026-8206 affecting the Kirki WordPress plugin. It is not part of a known exploit framework. The main exploit logic is in poc/poc_local.py, with poc/run_lab_poc.sh orchestrating execution against two local lab targets: a vulnerable Kirki 6.0.6 instance on 127.0.0.1:8081 and a patched 6.0.7 instance on 127.0.0.1:8082. The exploit capability is web-based unauthenticated account takeover via password reset misdelivery. The PoC sends a POST request to the WordPress REST route /?rest_route=/KirkiComponentLibrary/v1/kirki-forgot-password with a valid X-WP-Element-Nonce, target username admin, and attacker-controlled email attacker-lab@example.test. If vulnerable, the application generates a reset key for the admin account but sends the reset email to the attacker address. The script then inspects locally captured .eml files to confirm whether the reset link containing action=rp and login=admin was delivered to the attacker. The PoC intentionally stops short of resetting the password. Repository structure: docker-compose.yml defines two WordPress/MySQL stacks plus WP-CLI setup containers; vuln/Dockerfile and patched/Dockerfile build identical WordPress images with a custom sendmail capture hook; docker/capture-mail and docker/mail-capture.ini redirect outgoing mail into local artifact directories; scripts/setup-wordpress.sh installs and configures WordPress and the specified Kirki version; poc/poc_local.py performs the exploit attempt and validation; poc/run_lab_poc.sh clears artifacts, generates nonces via WP-CLI, and runs the PoC against both vulnerable and patched environments. Operationally, this is an OPERATIONAL PoC rather than a weaponized exploit: it contains a working exploit request and validation flow, but payload values are hardcoded for a safe local lab. Guardrails include loopback-only targeting by default, local mail capture, and no password change. The code also fingerprints the target by requesting /wp-content/plugins/kirki/readme.txt to extract the Stable tag version.
Repository contains a single Python exploit script and a README. The script is a multithreaded mass-exploitation tool targeting CVE-2026-8206 in the Kirki WordPress plugin (versions 6.0.6 and earlier). Its workflow is: normalize target URLs; detect Kirki installation/version by requesting plugin readme.txt or kirki.min.css under both 'kirki' and 'kirki-test' plugin directories; enumerate usernames (per README via /wp-json/wp/v2/users, with fallback to 'admin'); harvest nonce-like values from multiple public pages using many regex patterns; then submit POST requests to the vulnerable REST endpoint /wp-json/KirkiComponentLibrary/v1/kirki-forgot-password using the chosen username and an attacker-controlled email address. Successful exploitation is determined by a positive HTTP/application response indicating the email was sent, and successful targets are appended to res.txt. The code disables TLS verification warnings, uses requests plus ThreadPoolExecutor for concurrency, and is intended for bulk scanning/exploitation from a supplied targets file. This is a real exploit rather than a detector: its end goal is account takeover by rerouting password reset emails to the operator's mailbox.
This repository contains a single Python exploit script, CVE-2026-8206.py, implementing an automated web attack against a WordPress Kirki forgot-password workflow. The script defines a KirkiAutoExploit class with three main stages: (1) build a list of likely public pages that may expose a nonce, (2) fetch those pages and regex-scrape an X-WP-ELEMENT-NONCE or generic nonce value from HTML/JavaScript, and (3) submit a crafted POST request to the Kirki REST endpoint /wp-json/KirkiComponentLibrary/v1/kirki-forgot-password. The POST body includes a target username and an attacker-controlled email address, plus a JSON-encoded email body referencing a reset_link token, with the apparent goal of redirecting the password reset email to the attacker. The script is operational rather than a mere PoC because it performs the full attack flow automatically, including nonce discovery, request construction, and response handling. It is not a framework module and has a single obvious entry point under the __main__ block, taking target URL, victim username, and attacker email as command-line arguments. No shellcode or post-exploitation payload is present; the exploit capability is account takeover via password reset abuse on exposed vulnerable Kirki versions.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
48 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Referenced as a vulnerability identifier in a GitHub conversation about adding templates; no technical details are provided in the content.
A critical privilege escalation vulnerability in the WordPress Kirki plugin that allows unauthenticated attackers to reset arbitrary user passwords and hijack accounts, including administrator accounts, via a flawed REST API password reset mechanism.
A critical privilege escalation and account takeover vulnerability in the Kirki WordPress plugin caused by a flawed password reset mechanism that lets unauthenticated attackers send reset tokens for valid users to attacker-controlled email addresses.
A critical unauthenticated privilege escalation vulnerability in the Kirki-related WordPress frontend page building extension caused by a logic flaw in a custom REST API password reset workflow, allowing attackers to take over privileged WordPress accounts.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.