basicsecurity.net
Proof, not just disclosure.
Threats / Qlik / CVE-2023-41266
CVE-2023-41266 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Qlik Sense vulnerability

Qlik Sense contains a path traversal vulnerability allowing unauthenticated remote attackers to create anonymous sessions and access unauthorized endpoints.

Verdict

Today item, not a backlog item.

A critical unauthenticated path traversal flaw in Qlik Sense enables attackers to bypass authentication, establish anonymous sessions, and pivot to restricted functionality. Active exploitation and ransomware deployment confirm severe real-world risk.

CISA KEV Yes · 2023-12-073Ransomware use Flagged3EPSS 0.84966 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 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 2023-12-07), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.84966 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Qlik, Sense. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious HTTP requests exploiting path traversal to bypass authentication controls.
Business
Authentication mechanisms fail to protect sensitive endpoints from unauthenticated access.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I establish an anonymous session without credentials, gaining a foothold in the application.
Business
Session management allows unauthorized actors to interact with the platform as valid users.
3

Lateral reach — past segmentation narrative 3

Attacker
I enumerate and access unauthorized endpoints to extract data or identify further attack vectors.
Business
Sensitive business intelligence, configurations, and user data become accessible to external threat actors.
4

Data at risk — exfiltration narrative 4

Attacker
I leverage endpoint access to deploy ransomware or establish persistence for follow-on attacks.
Business
Systems become compromised, leading to data encryption, operational disruption, and extortion demands.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.