Kirki WordPress Plugin < 6.2.5 reCAPTCHA Bypass via Missing Token
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Kirki plugin for WordPress, prior to version 6.2.5, is affected. A flaw in its reCAPTCHA check lets anyone submit website forms without passing the verification, enabling unlimited spam submissions that can trigger notification emails, webhooks, and database writes.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Themeum Kirki
fixed in 6.2.5