# CVE-2019-3911: Cross-site scripting in LabKey Server Community Edition

> Unauthenticated attackers can inject arbitrary JavaScript via the onerror parameter in LabKey Server, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2x5v-3qcr-cj3f

## What is CVE-2019-3911?

CVE-2019-3911 is a medium-severity cross-site scripting vulnerability in Tenable LabKey Server Community Edition, published on 30 Jan 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Reflected cross-site scripting (XSS) vulnerability in LabKey Server Community Edition before 18.3.0-61806.763 allows an unauthenticated remote attacker to inject arbitrary javascript via the onerror parameter in the /__r2/query endpoints.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Labkey Labkey Server.

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

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

## Is CVE-2019-3911 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-3911 exists.

Public exploit code:

- LabKey Server Community Edition <18.3.0 - Cross-Site Scripting (nuclei): http/cves/2019/CVE-2019-3911.yaml

## Other vulnerabilities in Tenable LabKey Server Community Edition

- [CVE-2019-9926](https://insights.sbomify.com/CVE-2019-9926/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-9757](https://insights.sbomify.com/CVE-2019-9757/): XML external entity in n/a (high 7.5)
- [CVE-2019-3912](https://insights.sbomify.com/CVE-2019-3912/): Open redirect in LabKey Server Community Edition (medium 6.1)
- [CVE-2019-9758](https://insights.sbomify.com/CVE-2019-9758/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2019-3913](https://insights.sbomify.com/CVE-2019-3913/): Command injection in LabKey Server Community Edition (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3911 is a medium-severity cross-site scripting vulnerability in Tenable LabKey Server Community Edition, published on 30 Jan 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-3911 exists.

Affected product: Tenable LabKey Server Community Edition. 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-3911/ (Markdown: https://insights.sbomify.com/CVE-2019-3911/index.md)
```

## Sources

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

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