# CVE-2019-19289: A vulnerability has been identified in XHQ (All Versions < 6.1).


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Dec 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gfm3-3hp2-f82x

## What is CVE-2019-19289?

CVE-2019-19289 is a high-severity vulnerability in Siemens XHQ, published on 14 Dec 2020. 

### Official description

A vulnerability has been identified in XHQ (All Versions < 6.1). The web interface could allow a Cross-Site Request Forgery (CSRF) attack if an unsuspecting user is tricked into accessing a malicious link.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-19289?

It affects 1 product.


Products: Siemens Xhq.

## How do I fix CVE-2019-19289?

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

## Is CVE-2019-19289 being exploited?

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

## Other vulnerabilities in Siemens XHQ

- [CVE-2019-13932](https://insights.sbomify.com/CVE-2019-13932/): Other in XHQ (critical 9.1)
- [CVE-2019-13930](https://insights.sbomify.com/CVE-2019-13930/): Cross-site request forgery in XHQ (high 8.1)
- [CVE-2019-19286](https://insights.sbomify.com/CVE-2019-19286/): SQL injection in XHQ (high 7.2)
- [CVE-2019-19287](https://insights.sbomify.com/CVE-2019-19287/): Path traversal in XHQ (medium 6.5)
- [CVE-2019-19288](https://insights.sbomify.com/CVE-2019-19288/): Cross-site scripting in XHQ (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19289 and fix it if it is affected.

What it is: CVE-2019-19289 is a high-severity vulnerability in Siemens XHQ, published on 14 Dec 2020. 
Exploitation: There is no known exploitation of CVE-2019-19289 in the wild and no public exploit code.

Affected product: Siemens XHQ. 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-2019-19289/ (Markdown: https://insights.sbomify.com/CVE-2019-19289/index.md)
```

## Sources

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

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