Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-44qr-rrjg-2cqq | ApostropheCMS: CAPTCHA response token not URL-encoded |
Tue, 20 Oct 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apostrophecms
Apostrophecms apostrophecms Apostrophecms form Apostrophecms login-hcaptcha Apostrophecms login-recaptcha |
|
| Vendors & Products |
Apostrophecms
Apostrophecms apostrophecms Apostrophecms form Apostrophecms login-hcaptcha Apostrophecms login-recaptcha |
Tue, 20 Oct 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | ApostropheCMS: CAPTCHA response token not URL-encoded | |
| Weaknesses | CWE-116 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-20T17:33:28.418Z
Reserved: 2026-10-20T14:27:46.642Z
Link: CVE-2026-113667
No data.
Status : Deferred
Published: 2026-10-20T18:17:20.277
Modified: 2026-10-20T19:53:10.247
Link: CVE-2026-113667
No data.
OpenCVE Enrichment
Updated: 2026-10-20T20:29:26Z
Github GHSA