Answer in brief
CVE-2026-107762 records a High severity (CVSS 7.5) vulnerability in Kirki <= 6.3.2 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Exposure via Context Smuggling via 'context' Parameter. The current sources do not mark it as known exploited. The current feed maps themeum/Kirki – Freeform Page Builder, Website Builder & Customizer (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps themeum/Kirki – Freeform Page Builder, Website Builder & Customizer (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| themeum/Kirki – Freeform Page Builder, Website Builder & Customizergeneric | >=0 <=6.3.2 | Not reported |
Published upstream
Oct 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 17, 2026
The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.3.2 via the 'context' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to expose arbitrary users' sensitive profile data — including email address, display name, nicename, registration date, profile image URL, and any string-valued user meta fields such as first name, last name, nickname, description, and custom meta keys — via the REST response. Exploitation requires a published page that uses a Kirki template containing at least one user-type dynamic content block; target user IDs are enumerable via standard WordPress REST endpoints, making the only prerequisite the presence of such a template on the site.
Quoted source text, attributed separately from HOL analysis.