Kirki WordPress Plugin < 6.2.5 reCAPTCHA Bypass via Missing Token
Impact
The Kirki WordPress plugin before version 6.2.5 has a reCAPTCHA bypass vulnerability, allowing unauthenticated attackers to submit forms without verification. The weakness is due to the verify() method's early return on empty token values. This allows attackers to submit unlimited forms, triggering notifications and writes to the submissions table.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Themeum · VulnCheck
Kirki
1 range
Themeum · VulnCheck
Kirki
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 6.2.5
semver versions
Other versions: unaffected
Original source description
Kirki plugin for WordPress before 6.2.5 contains a reCAPTCHA bypass vulnerability that allows unauthenticated attackers to submit frontend forms without valid verification by omitting the g-recaptcha-token field from POST requests to the form submission endpoint. Attackers can exploit the verify() method's early return on empty token values to submit unlimited forms, triggering notification emails, webhooks, and unbounded writes to the submissions table without completing reCAPTCHA validation.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-112348View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.