# CVE-2026-113667: ApostropheCMS: CAPTCHA response token not URL-encoded


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-44qr-rrjg-2cqq

## What is CVE-2026-113667?

CVE-2026-113667 is a medium-severity vulnerability in @apostrophecms apostrophe, published on 20 Oct 2026. 

### Official 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.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-113667?

6 open source packages ship an affected version, including @apostrophecms/form, @apostrophecms/login-hcaptcha and @apostrophecms/login-recaptcha.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@apostrophecms/form` | npm | All versions | 1.5.5 |
| `@apostrophecms/form` | npm | All versions | 1.5.5 |
| `@apostrophecms/login-hcaptcha` | npm | All versions | 1.3.0 |
| `@apostrophecms/login-hcaptcha` | npm | All versions | 1.3.0 |
| `@apostrophecms/login-recaptcha` | npm | All versions | 1.2.1 |
| `@apostrophecms/login-recaptcha` | npm | All versions | 1.2.1 |

## How do I fix CVE-2026-113667?

Upgrade @apostrophecms/form to 1.5.5 or later.

## Is CVE-2026-113667 being exploited?

There is no known exploitation of CVE-2026-113667 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113667 and fix it if it is affected.

What it is: CVE-2026-113667 is a medium-severity vulnerability in @apostrophecms apostrophe, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113667 in the wild and no public exploit code.

Affected packages and fixed versions:
- @apostrophecms/form (npm): affected all versions; fixed in 1.5.5
- @apostrophecms/form (npm): affected all versions; fixed in 1.5.5
- @apostrophecms/login-hcaptcha (npm): affected all versions; fixed in 1.3.0
- @apostrophecms/login-hcaptcha (npm): affected all versions; fixed in 1.3.0
- @apostrophecms/login-recaptcha (npm): affected all versions; fixed in 1.2.1
- @apostrophecms/login-recaptcha (npm): affected all versions; fixed in 1.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113667/ (Markdown: https://insights.sbomify.com/CVE-2026-113667/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113667
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113667
- OSV: https://osv.dev/vulnerability/CVE-2026-113667

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113667/
Summaries are generated and may contain mistakes; the official description above is the record.