What is CVE-2026-113667?

CVE-2026-113667 is a medium-severity security vulnerability in @apostrophecms/form (npm), affecting versions < 1.5.5. It is fixed in 1.5.5, 1.2.1, 1.3.0.

Which packages are affected by CVE-2026-113667?

@apostrophecms/form (npm) versions < 1.5.5; @apostrophecms/login-recaptcha (npm) versions < 1.2.1; @apostrophecms/login-hcaptcha (npm) versions < 1.3.0.

Is there a fix for CVE-2026-113667?

Yes. CVE-2026-113667 is fixed in 1.5.5, 1.2.1, 1.3.0. Upgrade to this version or later.

Is CVE-2026-113667 exploitable, and should I be worried?

Whether CVE-2026-113667 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-113667 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-113667 in @apostrophecms/form

Q: Which packages are affected by CVE-2026-113667?

@apostrophecms/form (npm) versions < 1.5.5; @apostrophecms/login-recaptcha (npm) versions < 1.2.1; @apostrophecms/login-hcaptcha (npm) versions < 1.3.0.

Q: Is there a fix for CVE-2026-113667?

Yes. CVE-2026-113667 is fixed in 1.5.5, 1.2.1, 1.3.0. Upgrade to this version or later.

Q: Is CVE-2026-113667 exploitable, and should I be worried?

Whether CVE-2026-113667 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-113667 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-113667?

Upgrade: @apostrophecms/form to 1.5.5 or later, @apostrophecms/login-recaptcha to 1.2.1 or later, @apostrophecms/login-hcaptcha to 1.3.0 or later.

Summary

ApostropheCMS: CAPTCHA response token not URL-encoded

Summary
Form and login CAPTCHA verification interpolate the user-supplied widget token unencoded into the server-side verification URL/body, allowing a crafted token to inject query parameters into the reCAPTCHA/hCaptcha verify request.

Details

packages/form/lib/recaptcha.js:39, recaptchaUri = 'https://www.google.com/recaptcha/api/siteverify?secret=${recaptchaSecret}&response=${input.recaptcha}'
packages/login-recaptcha/index.js:44, same pattern for login
packages/login-hcaptcha/index.js:47, body: 'response=${token}&secret=${secret}'

PoC

input.recaptcha = 'attacker_token&secret=INJECTED_SECRET&something=1'
→ resulting verify URL:
   https://www.google.com/recaptcha/api/siteverify?secret=<real>&response=attacker_token&secret=INJECTED_SECRET&something=1
# (replicated exactly from recaptcha.js:39)

Impact
Low: a crafted token smuggles extra key=value pairs (secret, extra response) into the outbound verify call, forcing verification failures (DoS of the captcha gate and of captcha-gated login/form flows) and enabling automated bypass probing; no secret exfiltration.

Remediation, Build the verify request with URL + searchParams (or encodeURIComponent on both secret and response), and validate the token against ^[A-Za-z0-9._-]{1,2048}$ before use.

Impact

Affected versions

@apostrophecms/form (< 1.5.5) @apostrophecms/login-recaptcha (< 1.2.1) @apostrophecms/login-hcaptcha (< 1.3.0)

Security releases

@apostrophecms/form → 1.5.5 (npm) @apostrophecms/login-recaptcha → 1.2.1 (npm) @apostrophecms/login-hcaptcha → 1.3.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

@apostrophecms/form to 1.5.5 or later; @apostrophecms/login-recaptcha to 1.2.1 or later; @apostrophecms/login-hcaptcha to 1.3.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-113667? CVE-2026-113667 is a medium-severity security vulnerability in @apostrophecms/form (npm), affecting versions < 1.5.5. It is fixed in 1.5.5, 1.2.1, 1.3.0.
Which packages are affected by CVE-2026-113667?
- @apostrophecms/form (npm) (versions < 1.5.5)
- @apostrophecms/login-recaptcha (npm) (versions < 1.2.1)
- @apostrophecms/login-hcaptcha (npm) (versions < 1.3.0)
Is there a fix for CVE-2026-113667? Yes. CVE-2026-113667 is fixed in 1.5.5, 1.2.1, 1.3.0. Upgrade to this version or later.
Is CVE-2026-113667 exploitable, and should I be worried? Whether CVE-2026-113667 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-113667 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-113667?
- Upgrade @apostrophecms/form to 1.5.5 or later
- Upgrade @apostrophecms/login-recaptcha to 1.2.1 or later
- Upgrade @apostrophecms/login-hcaptcha to 1.3.0 or later

Other vulnerabilities in @apostrophecms/form

CVE-IDSeverityPackage summary

CVE-2026-113656Medium@apostrophecms/form: ApostropheCMS: Unauthenticated unbounded multipart upload → disk-exhaustion DoS