Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running Kirki ≤ 6.0.11
-
DeliverySend unauthenticated POST to admin-ajax.php with action=get_single_symbol
-
ExploitSupply sequential integer post IDs
-
ExecutionReceive builder metadata and rendered HTML for each kirki_symbol post
-
ImpactExtract unpublished draft content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
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 | The Kirki plugin (version ≤ 6.0.11) must be installed and active on the WordPress site. The target site must have at least one post of the kirki_symbol custom post type (created through the Kirki builder workflow). No authentication, no special configuration, and no user interaction are required - the CVSS vector AV:N/AC:L/PR:N/UI:N confirms this is exploitable against default plugin installations over the network. Exploitation is limited to kirki_symbol post type content only; general WordPress posts, pages, or other post types are not exposed through this endpoint. The practical impact is further bounded by whether the site stores sensitive pre-publication content in kirki_symbol posts. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N scores 5.3 (Medium). The attack vector is network, complexity is low, no privileges or user interaction are required, and scope is unchanged with only low confidentiality impact - meaning the exposure is bounded to kirki_symbol post content rather than broader site secrets. No EPSS score was provided in the available data, limiting probabilistic exploitation comparison. The vulnerability is not listed in CISA KEV, and no public POC has been identified at time of analysis. However, the automatable nature of post ID enumeration (no brute-forcing, just sequential integers) means the effective attack complexity is extremely low in practice, and the CVSS AC:L rating accurately reflects this. The primary real-world concern is exposure of pre-publication draft content - business logic, unreleased marketing copy, or staged page designs - which may carry confidentiality value disproportionate to the 'Low' CVSS C metric. Sites not using the kirki_symbol post type for sensitive staged content face materially lower risk. |
| Exploit ScenarioDerived | An attacker issues a series of HTTP POST requests to the target WordPress site's wp-admin/admin-ajax.php endpoint, specifying action=get_single_symbol and incrementing the post ID parameter from 1 upward. Because no authorization check is performed, the server returns the full builder metadata and rendered HTML for each matching kirki_symbol post, including any that are in draft or pending status and not yet publicly visible. This enumeration can be fully automated with a simple script requiring no credentials or prior site knowledge. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 02, 2026
Unauthenticated sensitive information exposure in the Kirki - Freeform Page Builder, Website Builder & Customizer WordPress plugin (versions through 6.0.11) permits any remote attacker to retrieve the full builder metadata and rendered HTML of any kirki_symbol post - including unpublished drafts - by issuing a crafted AJAX request with a sequential WordPress post ID. The root cause is a missing authorization check (CWE-862) in the get_single_symbol AJAX handler registered in includes/Ajax.php, confirmed by Wordfence. No active exploitation is confirmed in CISA KEV, and no EPSS data was provided, but the trivially automatable nature of post ID enumeration against an unauthenticated network endpoint elevates practical risk above the raw CVSS 5.3 score suggests.
RemediationAI
A fix has been committed to the WordPress plugin repository as changeset 3584702 (https://plugins.trac.wordpress.org/changeset?old=3584702%40kirki&new=3584702%40kirki); however, the exact patched release version number is not independently confirmed from the available data - update to the latest available version in the WordPress plugin directory and verify it is newer than 6.0.11. As a compensating control if immediate upgrade is not possible, consider blocking unauthenticated access to WordPress AJAX endpoints (wp-admin/admin-ajax.php) at the web server or WAF layer for requests specifying the get_single_symbol action - note this will disable the front-end symbol-loading functionality for anonymous visitors. Alternatively, if no site visitors require access to kirki_symbol post rendering while unauthenticated, restricting the endpoint via a firewall rule to authenticated sessions only eliminates the exposure with minimal functional impact.
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 the Kirki plugin's AJAX subsystem, specifically the get_single_symbol action handler defined in includes/Ajax/Symbol.php (lines 145 and 245, as seen in plugin tags 6.0.5 and 6.0.9) and registered in includes/Ajax.php (line 73). WordPress AJAX endpoints registered via wp_ajax_nopriv_ (or equivalent no-auth hooks) are accessible to unauthenticated users. CWE-862 (Missing Authorization) confirms that the handler performs no capability or ownership check before returning post content. The affected CPE is cpe:2.3:a:themeum:kirki_-_freeform_page_builder,_website_builder_&_customizer:*:*:*:*:*:*:*:* (vendor: Themeum). Because WordPress auto-increments post IDs sequentially, an attacker can systematically enumerate all kirki_symbol posts without any prior knowledge of the site's content structure.
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:L/I:N/A:N
AJAX endpoint is unauthenticated and network-reachable by default; confidentiality impact is low as exposure is scoped to kirki_symbol post content only, with no integrity or availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 6.0.11 via the get_single_symbol. This makes it possible for unauthenticated attackers to extract the full builder metadata and rendered HTML of any kirki_symbol post - including unpublished drafts - by supplying a sequential WordPress post ID.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-41264
GHSA-v9qp-6jjw-6rfv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB