# CVE-2018-11719: XML external entity in n/a

> Xovis PC devices are vulnerable to XML External Entity attacks, allowing attackers to read sensitive files or cause denial of service.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w2j7-xp4w-prx7

## What is CVE-2018-11719?

CVE-2018-11719 is a medium-severity vulnerability in n/a, published on 30 Aug 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Xovis PC2, PC2R, and PC3 devices through 3.6.0 allow XXE.

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

## Which versions are affected by CVE-2018-11719?

It affects 3 products.


Products: Xovis Pc2 Firmware, Xovis Pc2r Firmware, Xovis Pc3 Firmware.

## How do I fix CVE-2018-11719?

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

## Is CVE-2018-11719 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11718](https://insights.sbomify.com/CVE-2018-11718/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-11720](https://insights.sbomify.com/CVE-2018-11720/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11719 and fix it if it is affected.

What it is: CVE-2018-11719 is a medium-severity vulnerability in n/a, published on 30 Aug 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11719 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-2018-11719/ (Markdown: https://insights.sbomify.com/CVE-2018-11719/index.md)
```

## Sources

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

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