How severe is CVE-2019-11628?

CVE-2019-11628 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2019-11628 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (58th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-11628?

CVE-2019-11628 primarily affects Qlik Qlikview Server. In total, 50 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-11628?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-11628 published?

CVE-2019-11628 was published on 2019-05-01 and last updated on 2026-06-17.

CVE-2019-11628

CVE-2019-11628 is a high-severity vulnerability in Qlik Qlikview Server with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-917.

Key facts

Severity: High (CVSS 3.x base score 8.2)
CVSS v2: 4.0
EPSS exploit prediction: 1% (58th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-917
Affected product: Qlik Qlikview Server
Published: 2019-05-01
Last modified: 2026-06-17

Description

An issue was discovered in QlikView Server before 11.20 SR19, 12.00 and 12.10 before 12.10 SR11, 12.20 before SR9, and 12.30 before SR2; and Qlik Sense Enterprise and Qlik Analytics Platform installations that lack these patch levels: February 2018 Patch 4, April 2018 Patch 3, June 2018 Patch 3, September 2018 Patch 4, November 2018 Patch 4, or February 2019 Patch 2. An authenticated user may be able to bypass intended file-read restrictions via crafted Browser requests.

Frequently asked questions

What is CVE-2019-11628?: An issue was discovered in QlikView Server before 11.20 SR19, 12.00 and 12.10 before 12.10 SR11, 12.20 before SR9, and 12.30 before SR2; and Qlik Sense Enterprise and Qlik Analytics Platform installations that lack these patch levels: February 2018 Patch 4, April 2018 Patch 3, June 2018 Patch 3, September 2018 Patch 4, November 2018 Patch 4, or February 2019 Patch 2. An authenticated user may be able to bypass intended file-read restrictions via crafted Browser requests.
How severe is CVE-2019-11628?: CVE-2019-11628 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2019-11628 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (58th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-11628?: CVE-2019-11628 primarily affects Qlik Qlikview Server. In total, 50 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-11628?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-11628 published?: CVE-2019-11628 was published on 2019-05-01 and last updated on 2026-06-17.

References

https://qliksupport.force.com/articles/000069985

Affected products (50)

cpe:2.3:a:qlik:qlikview_server:11.20:service_release_1:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_10:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_11:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_12:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_13:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_14:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_15:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_16:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_17:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_2:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_3:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_4:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_5:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_6:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_7:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_8:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:11.20:service_release_9:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.00:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_1:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_2:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_3:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_4:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_5:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_6:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_7:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_8:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.10:service_release_9:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.20:service_release_1:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.20:service_release_2:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.20:service_release_3:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.20:service_release_4:*:*:*:*:*:*
cpe:2.3:a:qlik:qlikview_server:12.30:service_release_1:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:april_2018:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:february_2018:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:february_2019:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:june_2017:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:june_2018:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:november_2017:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:november_2018:*:*:*:*:*:*:*
cpe:2.3:a:qlik:qlik_analytics:september_2017:*:*:*:*:*:*:*

Other CWE-917 vulnerabilities

CVE-2025-3322 — Critical (CVSS 10.0): An improper neutralization of inputs used in expression language allows remote code execution with the highest…
CVE-2022-22947 — Critical (CVSS 10.0): In spring cloud gateway versions prior to 3.1.1+ and 3.0.7+ , applications are vulnerable to a code injection attack…
CVE-2026-11561 — Critical (CVSS 9.8): Improper neutralization of special elements used in an expression language statement ('expression language injection')…
CVE-2026-22738 — Critical (CVSS 9.8): In Spring AI, a SpEL injection vulnerability exists in SimpleVectorStore when a user-supplied value is used as a…
CVE-2026-24713 — Critical (CVSS 9.8): Improper Input Validation vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 1.3.7,…
CVE-2023-51593 — Critical (CVSS 9.8): Voltronic Power ViewPower Pro Expression Language Injection Remote Code Execution Vulnerability. This vulnerability…

Browse all CWE-917 vulnerabilities →