<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>EEA - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/eea/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 29 Oct 2026 18:37:50 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/eea/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>@eeacms/volto-chatbot: Unauthenticated Danswer API Confused Deputy Proxy</title><link>https://feed.craftedsignal.io/briefs/2026-10-volto-chatbot-danswer-proxy/</link><pubDate>Thu, 29 Oct 2026 18:37:50 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-volto-chatbot-danswer-proxy/</guid><description>An unauthenticated Express middleware vulnerability in @eeacms/volto-chatbot allows remote attackers to proxy requests to the Danswer API using the server’s own privileged service credentials.</description><content:encoded><![CDATA[<p>The <code>@eeacms/volto-chatbot</code> package contains a configuration issue in its Express middleware that exposes an unauthenticated proxy to the Danswer API. The vulnerability (CWE-862) resides in the <code>/_v1_da/</code> route, which forwards requests to the configured <code>DANSWER_URL</code> without performing authorization checks or path validation. When the add-on is configured with <code>DANSWER_API_KEY</code> or session cookies, the middleware silently attaches these credentials to requests. An unauthenticated attacker can control the destination path and HTTP method, effectively acting as the service account to perform unauthorized actions against the Danswer backend.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies an instance of <code>@eeacms/volto-chatbot</code> accessible over the network.</li>
<li>The attacker sends a crafted, unauthenticated HTTP request to the <code>/_v1_da/</code> endpoint on the Volto server.</li>
<li>The <code>proxyMiddleware</code> intercepts the request without requiring authentication or session validation.</li>
<li>The middleware extracts the attacker-supplied path from the request URL.</li>
<li>The middleware constructs an upstream URL by appending the attacker's path to the configured <code>DANSWER_URL</code>.</li>
<li>The middleware silently attaches the server-side <code>DANSWER_API_KEY</code> or session cookie to the outbound request headers.</li>
<li>The middleware forwards the request to the Danswer API, which processes the action as a privileged command from the service account.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to perform actions as the Danswer service account. Depending on the service account's permissions, this may lead to the unauthorized disclosure of sensitive documents and conversation history, or the mutation of system state, such as deleting users or creating chat sessions.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade <code>@eeacms/volto-chatbot</code> to a patched version once released by the maintainers.</li>
<li>If a patch is unavailable, immediately restrict network access to the Volto server to trusted internal segments.</li>
<li>Implement a Web Application Firewall (WAF) rule to block all requests to the <code>/_v1_da/</code> path.</li>
<li>Audit Danswer API access logs for requests originating from the Volto server IP address with suspicious or administrative paths (e.g., <code>/admin/</code>).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application</category><category>proxy</category><category>api-security</category></item></channel></rss>