@eeacms/volto-chatbot has Unauthenticated Danswer API Confused Deputy Proxy
Affects @eeacms/volto-chatbotSource GCVE Database
CVSS 8.2 High : upgrade to 2.0.4 soon.
Data as of 29 Oct 2026, 17:11 UTC
- Patch
- Available – fixed in 2.0.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NWhat to do
Upgrade @eeacms/volto-chatbot to 2.0.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@eeacms/volto-chatbot | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in @eeacms/volto-chatbot version 2.0.4 that fixes this vulnerability. Users should upgrade to version 2.0.4 or later to remediate the issue. Until patched, no effective mitigation is described other than disabling or restricting access to the vulnerable middleware route. The vendor advisory confirms the fix in 2.0.4.
Description
@eeacms/volto-chatbot version prior to 2.0.4 contains an unauthenticated proxy vulnerability that allows attackers to invoke arbitrary Danswer API operations with server-side credentials. The middleware route '**/_v1_da/**' accepts any HTTP method and path without authentication or path restrictions, forwarding requests with attached API keys or session cookies. This enables a Confused Deputy attack where attackers can perform privileged actions on the upstream Danswer API as the configured service account.
References
- github.com/eea/volto-chatbot/security/advisories/GHSA-w9x9-j56r-h98r (opens in a new tab)
- github.com/eea/volto-chatbot/commit/eaf18b7c0f23560086b300bf0c5e62f9f76ad7b0 (opens in a new tab)
- github.com/eea/volto-chatbot (opens in a new tab)
- github.com/eea/volto-chatbot/releases/tag/2.0.4 (opens in a new tab)