Cpe:2.3:a:qanything:qanything:2.0.0:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3aqanythingqanything2.0.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 04 Sep 2026 15:30:50 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAuthentication Bypass in QAnything 2.0.0https://feed.craftedsignal.io/briefs/2026-09-qanything-auth-bypass/Fri, 04 Sep 2026 15:30:50 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-qanything-auth-bypass/QAnything 2.0.0 contains an authentication bypass vulnerability in multiple API endpoints that allows unauthenticated attackers to exfiltrate sensitive uploaded documents and knowledge base files.QAnything version 2.0.0 is affected by an authentication bypass vulnerability within its local document question-answering service. Specifically, the endpoints /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc lack proper authorization checks, enabling unauthenticated remote attackers to retrieve stored files. By identifying and manipulating file identifiers in requests to these endpoints, an attacker can obtain base64-encoded file contents or parsed document chunks. This flaw allows unauthorized access to cross-tenant knowledge base content, potentially leading to the leakage of intellectual property or sensitive business data uploaded to the QAnything platform. There is no evidence in the source that this is currently being exploited in the wild, but the vulnerability is high-severity due to the ease of access to stored documents.

Impact

Successful exploitation allows unauthenticated attackers to exfiltrate any document or file indexed by the QAnything 2.0.0 knowledge base, resulting in a total compromise of the confidentiality of the data stored within the platform.

Recommendation

  • Patch QAnything to the latest version immediately or restrict network access to the /api/local_doc_qa/ endpoints until a vendor-supplied update is applied.
  • Review web server access logs for repeated HTTP GET requests to the identified vulnerable endpoints originating from unexpected or unauthorized IP addresses.
  • Deploy WAF rules to intercept and block unauthenticated traffic directed at the specific /api/local_doc_qa/ paths identified in this brief.
]]>highthreatweb-applicationauthentication-bypasscve-2026-85671