Answer in brief
CVE-2026-113667 records a Medium severity (CVSS 5.3) vulnerability in ApostropheCMS: CAPTCHA response token not URL-encoded. The current sources do not mark it as known exploited. The current feed maps apostrophecms/apostrophe (generic), @apostrophecms/form (generic), @apostrophecms/login-hcaptcha (generic), @apostrophecms/login-recaptcha (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps apostrophecms/apostrophe (generic), @apostrophecms/form (generic), @apostrophecms/login-hcaptcha (generic), @apostrophecms/login-recaptcha (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| apostrophecms/apostrophegeneric | <4.33.0 | 4.33.0 |
| @apostrophecms/formgeneric | <1.5.5 | 1.5.5 |
| @apostrophecms/login-hcaptchageneric | <1.3.0 | 1.3.0 |
| @apostrophecms/login-recaptchageneric | <1.2.1 | 1.2.1 |
| @apostrophecms/formnpm | <1.5.5 | 1.5.5 |
| @apostrophecms/formnpm | >=0 <1.5.5 | 1.5.5 |
| @apostrophecms/login-hcaptchanpm | <1.3.0 | 1.3.0 |
| @apostrophecms/login-hcaptchanpm | >=0 <1.3.0 | 1.3.0 |
| @apostrophecms/login-recaptchanpm | <1.2.1 | 1.2.1 |
| @apostrophecms/login-recaptchanpm | >=0 <1.2.1 | 1.2.1 |
Published upstream
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.