LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48365: Qlik Sense Enterprise for Windows before August 2023 Patch 2 allows unauthenticated remote code execution,...

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.

CriticalCVSS 9.6Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-48365 is a critical Qlik Sense Enterprise for Windows flaw that can let a remote attacker reach backend functions through malformed HTTP headers. CISA lists it as known exploited, so exposed or outdated deployments should be treated as urgent business risk, not a routine maintenance item.

Executive priority

Treat this as a high-priority remediation item because it is critical, remotely exploitable, and in CISA KEV. Ask for a same-cycle inventory, patch plan, and exposure report.

Technical view

The issue is CWE-444 improper HTTP header validation in Qlik Sense Enterprise for Windows before listed patched versions. It allows HTTP request tunneling to the repository backend and can lead to unauthenticated remote code execution. The CVE notes it resulted from an incomplete fix for CVE-2023-41265.

Likely exposure

Exposure is likely where Qlik Sense Enterprise for Windows is running before the fixed patch levels, especially if reachable from untrusted networks. The source bundle does not identify other affected Qlik products.

Exploitation context

CISA KEV inclusion means known exploitation is documented. The provided sources do not include exploit volume, specific threat actors, or compromise indicators, so those details should not be assumed.

Researcher notes

Focus validation on version evidence and request-handling behavior around HTTP header parsing and backend repository access. The CVE explicitly links this to incomplete remediation for CVE-2023-41265, so regression coverage should include that bypass class.

Mitigation direction

  • Upgrade to a fixed Qlik Sense Enterprise for Windows patch level.
  • Use Qlik’s official advisory to select the correct supported patch.
  • Prioritize internet-facing or partner-accessible Qlik deployments.
  • Review exposure controls while patching is planned.
  • Check vendor guidance before relying on compensating controls.

Validation and detection

  • Inventory all Qlik Sense Enterprise for Windows servers.
  • Confirm installed release and patch level against fixed versions.
  • Verify vulnerable instances are not externally reachable.
  • Review logs for suspicious repository or tunneled backend requests.
  • Track remediation evidence for each affected server.
Prepared
Reviewed
Confidence
high
Sources
4

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-444: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-48365 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.6 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.6CVSS 3.1CriticalCVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N3.15.8Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2023-48365Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-444 · source CWE mapping

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.