Threats / Qlik / CVE-2023-48365
CVE-2023-48365
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Qlik Sense vulnerability
Qlik Sense contains an HTTP tunneling vulnerability allowing privilege escalation and arbitrary HTTP requests on backend servers. Actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
An unauthenticated or low-privileged attacker can exploit HTTP tunneling to bypass access controls, escalate privileges, and execute requests as the backend server. This enables lateral movement and system compromise in ransomware operations.
CISA KEV Yes · 2025-01-135Ransomware use Flagged5EPSS 0.24676 (verify live)6CVSS 9.63CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
12 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-01-13), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.24676 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.6 (CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N) · Affected: Qlik, Sense. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-444 HTTP Request Smuggling — weakness family: Web / client.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 425 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious HTTP requests that tunnel through Qlik Sense to reach backend infrastructure.
Business
Attackers gain unauthorized access to internal systems and data not directly exposed to the internet.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I escalate my privileges by exploiting the tunneling mechanism to execute requests with elevated backend permissions.
Business
Administrative or system-level access is compromised, enabling full infrastructure control.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the compromised backend access to deploy ransomware payloads across the network.
Business
Critical systems are encrypted and operations halt, resulting in ransom demands and business disruption.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05