# CVE-2020-37014: Tryton 5.4 - Persistent Cross-Site Scripting

> Remote attackers can inject malicious scripts via the user profile name field, executing code in user interfaces and potentially compromising accounts.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA: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:** 30 Jan 2026
- **Updated:** 14 May 2026
- **Also known as:** DEBIAN-CVE-2020-37014, GHSA-3vjv-ww5h-3x77

## What is CVE-2020-37014?

CVE-2020-37014 is a medium-severity cross-site scripting vulnerability in Tryton, published on 30 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Tryton 5.4 contains a persistent cross-site scripting vulnerability in the user profile name input that allows remote attackers to inject malicious scripts. Attackers can exploit the vulnerability by inserting script payloads in the name field, which execute in the frontend and backend user interfaces.

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

## Which versions are affected by CVE-2020-37014?


## How do I fix CVE-2020-37014?

Upgrade to a fixed version.

## Is CVE-2020-37014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37014 and fix it if it is affected.

What it is: CVE-2020-37014 is a medium-severity cross-site scripting vulnerability in Tryton, published on 30 Jan 2026. Any signed-in user can exploit it over the network, 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-2020-37014 exists.

Affected product: Tryton. 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-2020-37014/ (Markdown: https://insights.sbomify.com/CVE-2020-37014/index.md)
```

## Sources

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

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