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

> Attackers can execute arbitrary scripts in user browsers due to missing XSS protections in RainLoop Webmail, potentially leading to session hijacking.

- **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:** Yes
- **Published:** 20 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v8j5-m4qg-vx9m, UBUNTU-CVE-2019-13389

## What is CVE-2019-13389?

CVE-2019-13389 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Mar 2020. 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

RainLoop Webmail before 1.13.0 lacks XSS protection mechanisms such as xlink:href validation, the X-XSS-Protection header, and the Content-Security-Policy header.

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

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

It affects 1 product.


Products: Rainloop Webmail.

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

Upgrade to a fixed version.

## Is CVE-2019-13389 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29360](https://insights.sbomify.com/CVE-2022-29360/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13389 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-13389 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-13389/ (Markdown: https://insights.sbomify.com/CVE-2019-13389/index.md)
```

## Sources

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

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