Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconEnumerate WordPress usernames via REST API
-
DeliverySubmit password reset with admin username and attacker email
-
ExploitPlugin emails reset token to attacker
-
InstallAttacker sets new admin password
-
C2Log in as administrator
-
ExecuteInstall backdoor plugin for persistence
-
ImpactExfiltrate data and pivot
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) the target WordPress site to have Kirki Freeform Page Builder version 6.0.0-6.0.6 installed and active with its front-end password reset form reachable, and (2) the attacker to know or enumerate a valid username on the site (administrator usernames are the high-value target and are commonly exposed via /wp-json/wp/v2/users, /?author=N redirects, or author archive pages). No authentication, no user interaction from the victim, and no non-default plugin configuration are required - the vulnerable code path is the default password-reset handler shipped with the affected versions. Limiting factors: sites that have disabled user enumeration, restricted the plugin's reset endpoint via WAF, or use email-based login only may raise the bar, but none of these are default WordPress hardening. |
| Impact | The CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H) is well-justified: exploitation is remote, requires no authentication, no user interaction, and yields full administrator takeover when an admin username is known - and WordPress administrator usernames are often enumerable via author archives, REST API (/wp-json/wp/v2/users), or login error timing. SSVC mapping would likely score Exploitation=PoC-likely, Automatable=YES (single HTTP request, scriptable across discovered Kirki installs), Technical Impact=Total. EPSS and KEV data are not provided in the input, so real-world exploitation prevalence cannot be quantified yet, but Wordfence-reported WordPress plugin flaws with trivial exploitation routinely see mass scanning within days of disclosure. The main mitigating factor is that the attacker must know or enumerate a valid username - a low bar on most WordPress deployments. This should be treated as a high-priority patch, not a paper tiger. |
| Exploit ScenarioDerived | An attacker enumerates the administrator username of a target WordPress site via the public REST API or author archive, then submits a password reset request to the Kirki front-end handler supplying the admin username together with their own attacker@example.com email address. The plugin generates a valid reset token for the administrator account and emails the reset link to the attacker, who clicks it, sets a new password, and logs in as administrator - leading to full site compromise, plugin installation for persistence, and content or credential theft. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 02, 2026
Account takeover in the Kirki Freeform Page Builder WordPress plugin (versions 6.0.0 through 6.0.6) allows unauthenticated remote attackers to hijack any registered account, including administrators, by redirecting password reset links to attacker-controlled email addresses. The flaw stems from the plugin honoring an arbitrary email value supplied alongside a valid username in password reset requests, breaking the trust binding between account and recovery destination. No public exploit identified at time of analysis, but the trivial nature of the bug and Wordfence's published advisory make weaponization straightforward.
RemediationAI
Upstream fix available (changeset 3530843); released patched version not independently confirmed in the input, but the vulnerability spans through 6.0.6, so upgrade to the next published Kirki release (6.0.7 or later) as soon as it appears in the WordPress.org plugin repository - verify the installed version is greater than 6.0.6 in wp-admin > Plugins. As an immediate workaround, deactivate the Kirki plugin if the front-end customizer features are non-essential, which fully eliminates exposure but disables any Kirki-driven UI components on the site. If deactivation is not viable, restrict access to the plugin's password reset endpoint at the web server or WAF layer (Wordfence and similar WAFs typically ship a virtual patch shortly after Wordfence disclosure - confirm the rule is active), and harden username discoverability by disabling REST user enumeration and author archives. Forcing a site-wide password reset for administrators after patching is prudent given the silent nature of this takeover. Reference the Wordfence advisory and trac changeset above for vendor-confirmed details.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in Kirki's ComponentLibrary password reset workflow (CompLibFormHandler.php and ElementGenerator.php), which implements a custom front-end password reset form rather than relying on WordPress core's wp_lostpassword_url() flow. Per the referenced source lines, the handler resolves the target user via the supplied username but then dispatches the reset email to a separately supplied 'email' parameter without verifying that the address matches the user's stored email. This is a textbook CWE-269 (Improper Privilege Management) manifestation realized through broken trust delegation - the recovery channel is attacker-controlled rather than user-controlled. Kirki is a widely deployed WordPress customizer and page-builder framework (themeum:kirki per CPE), so any site running an affected version with public registration or known usernames is exposed.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (Wordfence) · only source for this CVE.
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Executive ViewAI
The Kirki Freeform Page Builder WordPress plugin (versions 6.0.0-6.0.6) contains a critical account takeover vulnerability allowing unauthenticated attackers to hijack any registered account including site administrators by redirecting password reset emails. Organizations using this plugin face immediate risk of complete website compromise, as attackers with admin access can inject malicious code, modify site content, and steal sensitive data. All affected sites should treat this as a priority security incident requiring immediate remediation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Immediately disable the Kirki plugin to prevent exploitation; (2) Implement multi-factor authentication (MFA) on all WordPress administrator accounts to limit account takeover impact; (3) Enforce strong password policies and consider disabling the password reset function for admin accounts if operationally feasible; (4) Monitor audit logs for unauthorized administrator account activity; (5) Deploy a Web Application Firewall (WAF) to detect and block suspicious password reset requests if the plugin must remain active during transition.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-33881
GHSA-gr32-6rr4-7px2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB