CVE-2026-113667: medium-severity vulnerability in apostrophecms apostrophe
ApostropheCMS: CAPTCHA response token not URL-encoded
Published · Updated
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.4%
exploitation probability
0.4%top 70% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Affected products
@apostrophecms · form@apostrophecms · login-hcaptcha@apostrophecms · login-recaptchaapostrophecms · apostropheRelated CVEs — apostrophecms apostrophe
In the same product, most dangerous first.
References
https://github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845cehttps://github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350https://github.com/apostrophecms/apostrophe/releases/tag/@apostrophecms/form@1.5.5https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-44qr-rrjg-2cqq