CVE-2026-107762 json
Kirki <= 6.3.2 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Exposure via Context Smuggling via 'context' Parameter
published 23d ago modified 21d ago also EUVD-2026-103213
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-107762 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 22d ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- themeum Kirki – Freeform Page Builder, Website Builder & Customizer
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/1f2fd69f-d432-4eb2-9d28-cfd7dd100e82?source=cve
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.2/includes/API/Frontend/Controllers/CollectionController.php#L179
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.2/includes/API/Frontend/Controllers/FrontendRESTController.php#L64
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.2/includes/Frontend/Preview/Utils.php#L466
- plugins.trac.wordpress.org /browser/kirki/tags/6.3.2/includes/HelperFunctions.php#L1152
- plugins.trac.wordpress.org /changeset/3743904/kirki/trunk/includes/API/Frontend/Controllers/CollectionController.php
Sources
- CVE List CVE-2026-107762
- NVD CVE-2026-107762
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.