https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 21 Oct 2026 20:27:31 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-113667 <p>ApostropheCMS is an open-source Node.js content management system. Prior to 1.5.5 of the Form add-on, 1.2.1 of login-recaptcha, and 1.3.0 of login-hcaptcha, these three CAPTCHA integrations interpolate an unencoded user-supplied response token into the provider verification request. Crafted tokens can smuggle request parameters and disrupt CAPTCHA verification and CAPTCHA-gated form or login flows; automated bypass probing is possible, but a successful CAPTCHA bypass or secret disclosure is not established. This issue is fixed in Form 1.5.5, login-recaptcha 1.2.1, and login-hcaptcha 1.3.0.</p> <p>ApostropheCMS is an open-source Node.js content management system. Prior to 1.5.5 of the Form add-on, 1.2.1 of login-recaptcha, and 1.3.0 of login-hcaptcha, these three CAPTCHA integrations interpolate an unencoded user-supplied response token into the provider verification request. Crafted tokens can smuggle request parameters and disrupt CAPTCHA verification and CAPTCHA-gated form or login flows; automated bypass probing is possible, but a successful CAPTCHA bypass or secret disclosure is not established. This issue is fixed in Form 1.5.5, login-recaptcha 1.2.1, and login-hcaptcha 1.3.0.</p> https://db.gcve.eu/vuln/fkie_cve-2026-113667 https://db.gcve.eu/vuln/ghsa-44qr-rrjg-2cqq <p><strong>Affected:</strong> npm: @apostrophecms/form, npm: @apostrophecms/login-recaptcha, npm: @apostrophecms/login-hcaptcha</p> <p>**Summary** Form and login CAPTCHA verification interpolate the user-supplied widget token unencoded into the server-side verification URL/body, allowing a crafted token to inject query parameters into the reCAPTCHA/hCaptcha verify request.</p> <p>**Details** - `packages/form/lib/recaptcha.js:39` — `recaptchaUri = &#39;https://www.google.com/recaptcha/api/siteverify?secret=${recaptchaSecret}&amp;response=${input.recaptcha}&#39;` - `packages/login-recaptcha/index.js:44` — same pattern for login - `packages/login-hcaptcha/index.js:47` — `body: &#39;response=${token}&amp;secret=${secret}&#39;`</p> <p>**PoC** ``` input.recaptcha = &#39;attacker_token&amp;secret=INJECTED_SECRET&amp;something=1&#39; → resulting verify URL: https://www.google.com/recaptcha/api/siteverify?secret=&lt;real&gt;&amp;response=attacker_token&amp;secret=INJECTED_SECRET&amp;something=1 # (replicated exactly from recaptcha.js:39) ```</p> <p>**Impact** Low: a crafted token smuggles extra `key=value` pairs (`secret`, extra `response`) into the outbound verify call, forcing verification failures (DoS of the captcha gate and of captcha-gated login/form flows) and enabling automated bypass probing; no secret exfiltration.</p> <p>**Remediation** — Build the verify request with `URL` + `searchParams` (or `encodeURIComponent` on both `secret` and `response`), and validate the token against `^[A-Za-z0-9._-]{1,2048}$` before use.</p> <p><strong>Affected:</strong> npm: @apostrophecms/form, npm: @apostrophecms/login-recaptcha, npm: @apostrophecms/login-hcaptcha</p> <p>**Summary** Form and login CAPTCHA verification interpolate the user-supplied widget token unencoded into the server-side verification URL/body, allowing a crafted token to inject query parameters into the reCAPTCHA/hCaptcha verify request.</p> <p>**Details** - `packages/form/lib/recaptcha.js:39` — `recaptchaUri = &#39;https://www.google.com/recaptcha/api/siteverify?secret=${recaptchaSecret}&amp;response=${input.recaptcha}&#39;` - `packages/login-recaptcha/index.js:44` — same pattern for login - `packages/login-hcaptcha/index.js:47` — `body: &#39;response=${token}&amp;secret=${secret}&#39;`</p> <p>**PoC** ``` input.recaptcha = &#39;attacker_token&amp;secret=INJECTED_SECRET&amp;something=1&#39; → resulting verify URL: https://www.google.com/recaptcha/api/siteverify?secret=&lt;real&gt;&amp;response=attacker_token&amp;secret=INJECTED_SECRET&amp;something=1 # (replicated exactly from recaptcha.js:39) ```</p> <p>**Impact** Low: a crafted token smuggles extra `key=value` pairs (`secret`, extra `response`) into the outbound verify call, forcing verification failures (DoS of the captcha gate and of captcha-gated login/form flows) and enabling automated bypass probing; no secret exfiltration.</p> <p>**Remediation** — Build the verify request with `URL` + `searchParams` (or `encodeURIComponent` on both `secret` and `response`), and validate the token against `^[A-Za-z0-9._-]{1,2048}$` before use.</p> https://db.gcve.eu/vuln/ghsa-44qr-rrjg-2cqq