cve.bz

CVE-2026-113667 Improper Encoding or Escaping of Output

5.3 mediumEPSS 0.4%Fix available

Medium (5.3). EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @apostrophecms/form 1.5.5.

On this page
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.

Severity

CVSS 4.0

5.3 medium
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
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-116 Improper Encoding or Escaping of Output
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @apostrophecms/form (npm): fixed in 1.5.5
  • @apostrophecms/login-recaptcha (npm): fixed in 1.2.1
  • @apostrophecms/login-hcaptcha (npm): fixed in 1.3.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-113667 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113667?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113667?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-113667 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
apostrophecms apostrophe< 4.33.0
@apostrophecms form< 1.5.5
@apostrophecms login-hcaptcha< 1.3.0
@apostrophecms login-recaptcha< 1.2.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-44qr-rrjg-2cqqnpm@apostrophecms/form<1.5.51.5.5
GHSA-44qr-rrjg-2cqqnpm@apostrophecms/login-recaptcha<1.2.11.2.1
GHSA-44qr-rrjg-2cqqnpm@apostrophecms/login-hcaptcha<1.3.01.3.0

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON