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

> An attacker can exploit an XML External Entity vulnerability in SAP NetWeaver Application Server to read local files via a specific URI.

- **Severity:** Medium 6.4 (`CVSS:3.0/AC:L/AV:N/A:L/C:L/I:N/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hmph-2g6j-pvm5

## What is CVE-2015-7968?

CVE-2015-7968 is a medium-severity vulnerability in n/a, published on 9 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

nwbc_ext2int in SAP NetWeaver Application Server before Security Note 2183189 allows XXE attacks for local file inclusion via the sap/bc/ui2/nwbc/nwbc_ext2int/ URI.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 1 product.


Products: Sap Netweaver Application Server.

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

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

## Is CVE-2015-7968 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7968 is a medium-severity vulnerability in n/a, published on 9 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7968 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-7968/ (Markdown: https://insights.sbomify.com/CVE-2015-7968/index.md)
```

## Sources

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

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