CVE-2026-75891: Kirki (WordPress plugin) · Deserialization of Untrusted Data
Affects Kirki (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 27 Oct 2026, 07:27 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| themeumKirki – Freeform Page Builder, Website Builder & Customizer | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is available, restrict access to authenticated users and consider disabling or removing the Kirki plugin if possible to prevent exploitation.
Description
The Kirki plugin for WordPress up to version 6.2.5 contains a vulnerability that allows privilege escalation via PHP object injection. Authenticated users with Subscriber-level access or higher can exploit a missing capability check in the 'get-single-symbol' AJAX dispatcher branch to inject malicious PHP objects. This can lead to overwriting an administrator's password and gaining administrative access.