CVE-2026-112348

Kirki – Freeform Page Builder, Website Builder & Customizer <= 6.2.4 - Unauthenticated reCAPTCHA Validation Bypass

2026-10-30 00:00
Choriyev Qahramon

Strategic Overview

Status
Patched in 6.2.5
Affected Version
<= 6.2.4
CVSS
5.3Medium
Weakness type
CWE-693 · Protection Mechanism Failure
CVE
CVE-2026-112348
View all Kirki – Freeform Page Builder, Website Builder & Customizer vulnerabilities

At a glance

CVE-2026-112348 is a medium-severity Protection Mechanism Failure vulnerability in the Kirki WordPress plugin, affecting versions <= 6.2.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.2.5; sites on affected versions should update now. Disclosed October 2026, reported by Choriyev Qahramon.

Vulnerability Overview

The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Security Feature Bypass in all versions up to, and including, 6.2.4. This is due to an early return in the Recaptcha::verify() method when the supplied token is empty, allowing the check to be skipped entirely by omitting the g-recaptcha-token field from the POST request. This makes it possible for unauthenticated attackers to submit frontend forms without completing reCAPTCHA validation, triggering notification emails, webhooks, and unbounded writes to the submissions table. A form with reCAPTCHA enabled must be present on the site.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-693: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Remediation

Update to version 6.2.5, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Kirki 6.2.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C