How severe is CVE-2026-113667?

No CVSS score has been assigned to CVE-2026-113667 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-113667?

CVE-2026-113667 affects the following packages: @apostrophecms/form (npm), @apostrophecms/login-recaptcha (npm), @apostrophecms/login-hcaptcha (npm). Ecosystems affected: npm.

How do I fix CVE-2026-113667?

Update @apostrophecms/form to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-113667 is resolved across your whole dependency graph.

How do I detect CVE-2026-113667 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apostrophecms/form, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-113667 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-113667 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-113667 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-113667?

CVE-2026-113667 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-113667?

CVE-2026-113667 is classified as CWE-116 (CWE-116). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-113667 published, and has it been updated?

CVE-2026-113667 was published on October 20, 2026 and was last updated on October 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-113667 — @apostrophecms/form

Fix: apostrophecms/apostrophe@9500b8b

CVE-2026-113667 is a CWE-116 vulnerability in @apostrophecms/form. A fix is available for @apostrophecms/form — see the affected versions and patch details below.

ApostropheCMS: CAPTCHA response token not URL-encoded

Also known asGHSA-44qr-rrjg-2cqq

Published

Oct 20, 2026

Updated

Oct 22, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-113667.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

📦@apostrophecms/form📦@apostrophecms/login-recaptcha📦@apostrophecms/login-hcaptcha

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@apostrophecms/form`	all versions	1.5.5`npm install @apostrophecms/form@1.5.5`
📦npm	`@apostrophecms/login-recaptcha`	all versions	1.2.1`npm install @apostrophecms/login-recaptcha@1.2.1`
📦npm	`@apostrophecms/login-hcaptcha`	all versions	1.3.0`npm install @apostrophecms/login-hcaptcha@1.3.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apostrophecms/form, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @apostrophecms/form to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-113667 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

**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 = '

O3 Security · Impact-Aware SCA

Is CVE-2026-113667 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works