CVE-2026-12122
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 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.
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 plugin for WordPress contains an unauthenticated information disclosure vulnerability in the get_single_symbol function. Attackers can supply sequential WordPress post IDs to extract full builder metadata and rendered HTML from any kirki_symbol post type, including unpublished drafts, without any authentication or authorization checks.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Verify Kirki plugin is installedAccess WordPress admin panel, go to Plugins > Installed Plugins, and locate the Kirki plugin. Alternatively, check the /wp-content/plugins/kirki/ directory exists on the server.Affected if The Kirki plugin is present in the WordPress installation
-
Check installed Kirki plugin versionIn WordPress admin, click on the Kirki plugin to view details and note the version number. Alternatively, check the main plugin file (e.g., kirki.php) for the 'Version' header.Affected if The installed version is earlier than 6.0.12 (the fixed version)
-
Identify kirki_symbol post type postsIn WordPress admin, navigate to the Posts or custom post type section and look for 'kirki_symbol' post type entries. Query the wp_posts table directly: SELECT * FROM wp_posts WHERE post_type = 'kirki_symbol';Affected if Any kirki_symbol posts exist in the database, including unpublished drafts
-
Check for unauthenticated API exposureTest if the get_single_symbol function is accessible without authentication by making a request to the relevant AJAX endpoint or REST API route that handles kirki_symbol lookups (such as wp-admin/admin-ajax.php?action=get_single_symbol or similar).Affected if The endpoint returns builder metadata or rendered HTML without requiring login credentials
If Kirki plugin version is earlier than 6.0.12 and kirki_symbol posts exist in the database, the site is vulnerable to unauthenticated information disclosure.
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.12 or later which contains the security fix. Alternatively, temporarily disable the plugin or add firewall rules to block access to the vulnerable endpoint until an update can be applied.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12122 — 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-12122 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