{"answers":{"affected":"6 open source packages ship an affected version, including @apostrophecms/form, @apostrophecms/login-hcaptcha and @apostrophecms/login-recaptcha.","exploited":"There is no known exploitation of CVE-2026-113667 in the wild and no public exploit code.","fix":"Upgrade @apostrophecms/form to 1.5.5 or later.","what":"CVE-2026-113667 is a medium-severity vulnerability in @apostrophecms apostrophe, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-113667 and fix it if it is affected.\n\nWhat it is: CVE-2026-113667 is a medium-severity vulnerability in @apostrophecms apostrophe, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-113667 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @apostrophecms/form (npm): affected all versions; fixed in 1.5.5\n- @apostrophecms/form (npm): affected all versions; fixed in 1.5.5\n- @apostrophecms/login-hcaptcha (npm): affected all versions; fixed in 1.3.0\n- @apostrophecms/login-hcaptcha (npm): affected all versions; fixed in 1.3.0\n- @apostrophecms/login-recaptcha (npm): affected all versions; fixed in 1.2.1\n- @apostrophecms/login-recaptcha (npm): affected all versions; fixed in 1.2.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-113667/ (Markdown: https://insights.sbomify.com/CVE-2026-113667/index.md)","id":"CVE-2026-113667","markdown":"https://insights.sbomify.com/CVE-2026-113667/index.md","name":"CVE-2026-113667","record":{"aliases":["GHSA-44qr-rrjg-2cqq"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ApostropheCMS: CAPTCHA response token not URL-encoded","id":"CVE-2026-113667","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":6,"n_references":4,"next":{"headline":"ApostropheCMS: :_id/locales REST route omits the public-API authorization gate its sibling read routes enforce (unauthenticated doc-existence + locale metadata disclosure)","id":"CVE-2026-113668"},"packages":[{"ecosystem":"npm","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/form","purl":null,"source":"GHSA-44qr-rrjg-2cqq"},{"ecosystem":"npm","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/form","purl":"pkg:npm/%40apostrophecms/form","source":"GHSA-44qr-rrjg-2cqq"},{"ecosystem":"npm","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/login-hcaptcha","purl":null,"source":"GHSA-44qr-rrjg-2cqq"},{"ecosystem":"npm","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/login-hcaptcha","purl":"pkg:npm/%40apostrophecms/login-hcaptcha","source":"GHSA-44qr-rrjg-2cqq"},{"ecosystem":"npm","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/login-recaptcha","purl":null,"source":"GHSA-44qr-rrjg-2cqq"},{"ecosystem":"npm","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/login-recaptcha","purl":"pkg:npm/%40apostrophecms/login-recaptcha","source":"GHSA-44qr-rrjg-2cqq"}],"prev":{"headline":"ApostropheCMS: Authenticated projection-exclusion prototype-member deletion in @apostrophecms/db-connect causes process-wide denial of service","id":"CVE-2026-113666"},"products":["apostrophe","form","login-hcaptcha","login-recaptcha"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-21","vendors":["@apostrophecms","apostrophecms"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-113667/"}