Skip to main content
Vulnerability Database/CVE-2026-113667

CVE-2026-113667: ApostropheCMS CAPTCHA Auth Bypass Vulnerability

CVE-2026-113667 is an authentication bypass flaw in ApostropheCMS CAPTCHA integrations that allows attackers to smuggle request parameters and disrupt verification flows. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-113667 Overview

ApostropheCMS contains an output encoding flaw [CWE-116] in three CAPTCHA integrations: the Form add-on, login-recaptcha, and login-hcaptcha. The affected modules interpolate an unencoded, user-supplied CAPTCHA response token directly into the verification request sent to the provider. Attackers can craft tokens that smuggle request parameters into the outbound verification call, disrupting CAPTCHA verification and the form or login flows that depend on it. Automated probing for CAPTCHA bypass is possible, though a confirmed bypass or secret disclosure has not been established. Maintainers resolved the issue in Form 1.5.5, login-recaptcha1.2.1, and login-hcaptcha1.3.0.

Critical Impact

Crafted CAPTCHA tokens can smuggle parameters into provider verification requests, degrading bot protection on CAPTCHA-gated login and form submission endpoints.

Affected Products

  • ApostropheCMS Form add-on prior to 1.5.5
  • ApostropheCMS login-recaptcha prior to 1.2.1
  • ApostropheCMS login-hcaptcha prior to 1.3.0

Discovery Timeline

  • 2026-10-20 - CVE-2026-113667 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-113667

Vulnerability Analysis

The three affected ApostropheCMS CAPTCHA integrations accept a client-supplied response token and forward it to the respective CAPTCHA provider (Google reCAPTCHA or hCaptcha) for verification. Instead of URL-encoding or otherwise sanitizing the token before composing the outbound HTTP request body, the module interpolates it directly into the request string. An attacker submitting a crafted token containing reserved characters such as & or = can inject additional parameters into the verification request. This causes the provider to receive a malformed or attacker-influenced verification payload, which can disrupt the CAPTCHA check and any login or form workflow that gates on its result.

Root Cause

The underlying defect is improper encoding of output passed to a downstream component [CWE-116]. The CAPTCHA verification helper treats user-controlled input as if it were already safe for inclusion in a request body, violating the trust boundary between the browser-supplied token and the server-to-server verification call. Because the provider parses the request body as application/x-www-form-urlencoded, injected &key=value pairs are parsed as legitimate fields.

Attack Vector

Exploitation requires only network access to a CAPTCHA-protected endpoint on a vulnerable ApostropheCMS site. An attacker submits a form or login request with a specially crafted g-recaptcha-response or h-captcha-response value. The payload includes reserved URL characters that smuggle fields such as a replacement secret or response parameter into the outbound verification request. Automated probing is feasible, but the public advisory notes that a successful CAPTCHA bypass or disclosure of the provider secret has not been demonstrated.

No verified proof-of-concept code is published for this issue. The upstream commits reference broader security advisory reconciliation rather than isolated exploitation code. See the GitHub Security Advisory GHSA-44qr-rrjg-2cqq for the authoritative technical description.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-113667

Indicators of Compromise

  • Form or login submissions containing CAPTCHA response tokens with URL-reserved characters such as &, =, or ? embedded in the value.
  • Outbound HTTPS requests from the ApostropheCMS host to www.google.com/recaptcha/api/siteverify or hcaptcha.com/siteverify carrying unexpected or duplicated query parameters.
  • Elevated rates of CAPTCHA verification failures or anomalous error-codes responses from the CAPTCHA provider.

Detection Strategies

  • Inspect web application logs for response or g-recaptcha-response parameters that exceed expected token length or contain reserved characters outside the standard token alphabet.
  • Correlate authentication and form submission telemetry with CAPTCHA provider verification outcomes to identify sessions where the server-side check behaves inconsistently.
  • Audit installed ApostropheCMS modules against the fixed versions @apostrophecms/form@1.5.5, login-recaptcha@1.2.1, and login-hcaptcha@1.3.0.

Monitoring Recommendations

  • Monitor spikes in failed logins or form submissions on CAPTCHA-gated endpoints that may indicate automated bypass probing.
  • Alert on repeated submissions from the same source IP with malformed CAPTCHA tokens.
  • Track egress traffic volume to CAPTCHA provider verification endpoints for sudden deviations from baseline.

How to Mitigate CVE-2026-113667

Immediate Actions Required

  • Upgrade the Form add-on to 1.5.5, login-recaptcha to 1.2.1, and login-hcaptcha to 1.3.0 on all ApostropheCMS deployments.
  • Rotate CAPTCHA provider secret keys if abnormal verification traffic has been observed prior to patching.
  • Review web server logs for prior exploitation attempts targeting CAPTCHA-protected endpoints.

Patch Information

Fixes are delivered in the ApostropheCMS Form Release 1.5.5, with corresponding patches in ApostropheCMS Commit Update and ApostropheCMS Commit Fix. Full advisory details are available in GHSA-44qr-rrjg-2cqq.

Workarounds

  • If immediate patching is not possible, deploy a web application firewall rule to reject form or login submissions whose CAPTCHA response token contains reserved URL characters.
  • Temporarily disable CAPTCHA-gated self-service flows that are not business-critical until the fixed module versions are installed.
bash
# Upgrade affected ApostropheCMS CAPTCHA modules
npm install @apostrophecms/form@1.5.5
npm install @apostrophecms/login-recaptcha@1.2.1
npm install @apostrophecms/login-hcaptcha@1.3.0

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.