https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-05T16:36:42.823979+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-364177 EUVD-2026-364177 2026-10-05T16:36:42.873102+00:00 EUVD-2026-364177 https://cve.radiocsirt.org/vuln/fkie_cve-2026-85602 fkie_cve-2026-85602 2026-10-05T16:36:42.873142+00:00

The Grav Form plugin (getgrav/grav-plugin-form) versions 8.0.6 through 9.1.19 select the reCAPTCHA version to validate based solely on which response field key is present in the submitted payload. On a site configured for reCAPTCHA v3, an anonymous attacker can place their v3 token under the v2 field name (g-recaptcha-response instead of token), causing validation to use the v2 branch, which never applies the score threshold or verifies the expected action. This results in a complete bypass of reCAPTCHA v3 bot protection. The issue is fixed in version 9.1.20.

 https://cve.radiocsirt.org/vuln/ghsa-v453-9p95-fp34 GHSA-v453-9p95-fp34 2026-10-05T16:36:42.873178+00:00

The Grav Form plugin (getgrav/grav-plugin-form) versions 8.0.6 through 9.1.19 select the reCAPTCHA version to validate based solely on which response field key is present in the submitted payload. On a site configured for reCAPTCHA v3, an anonymous attacker can place their v3 token under the v2 field name (g-recaptcha-response instead of token), causing validation to use the v2 branch, which never applies the score threshold or verifies the expected action. This results in a complete bypass of reCAPTCHA v3 bot protection. The issue is fixed in version 9.1.20.