# CVE-2015-3623: XML external entity in n/a

> Remote attackers can exploit an XML external entity flaw in QlikView AccessPoint to read arbitrary files and perform server-side request forgery.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m945-cp8g-j6x8

## What is CVE-2015-3623?

CVE-2015-3623 is a medium-severity vulnerability in n/a, published on 16 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XML external entity (XXE) vulnerability in QlikTech Qlikview before 11.20 SR12 allows remote attackers to conduct server-side request forgery (SSRF) attacks and read arbitrary files via crafted XML data in a request to AccessPoint.aspx.

## Which versions are affected by CVE-2015-3623?

It affects 1 product.


Products: Qlik Qlikview.

## How do I fix CVE-2015-3623?

No fix has been published for CVE-2015-3623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-3623 being exploited?

There is no known exploitation of CVE-2015-3623 in the wild and no public exploit code.

Public exploit code:

- Qlikview 11.20 SR11 - Blind XML External Entity Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-41989](https://insights.sbomify.com/CVE-2021-41989/): Information disclosure in n/a (high 7.8)
- [CVE-2022-42248](https://insights.sbomify.com/CVE-2022-42248/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3623 and fix it if it is affected.

What it is: CVE-2015-3623 is a medium-severity vulnerability in n/a, published on 16 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3623 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-3623/ (Markdown: https://insights.sbomify.com/CVE-2015-3623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-3623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-3623
- OSV: https://osv.dev/vulnerability/CVE-2015-3623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-3623/
Summaries are generated and may contain mistakes; the official description above is the record.