# CVE-2019-18347: Cross-site scripting in n/a

> Stored XSS in DAViCal allows attackers to execute JavaScript in other users' browsers via unsanitized user fields.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-18347, GHSA-92gq-cfj6-292h, UBUNTU-CVE-2019-18347

## What is CVE-2019-18347?

CVE-2019-18347 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored XSS issue was discovered in DAViCal through 1.1.8. It does not adequately sanitize output of various fields that can be set by unprivileged users, making it possible for JavaScript stored in those fields to be executed by another (possibly privileged) user. Affected database fields include Username, Display Name, and Email.

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

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

It affects 1 product.


Products: Davical Davical.

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

Upgrade to a fixed version.

## Is CVE-2019-18347 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18345](https://insights.sbomify.com/CVE-2019-18345/): Cross-site scripting in n/a (critical 9.3)
- [CVE-2019-18346](https://insights.sbomify.com/CVE-2019-18346/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18347 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-18347 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-2019-18347/ (Markdown: https://insights.sbomify.com/CVE-2019-18347/index.md)
```

## Sources

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

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