Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-112348medium6.9

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

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Themeum · VulnCheck

Kirki

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 6.2.5

semver versions

unaffected

unknown

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

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-112348

View 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.

CWE-693 ↗

Protection Mechanism Failure

VulnCheck

Related →
Contributing organizations · 1
VulnCheck

Assigning organization

2026-10-30

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources