# CVE-2020-37018: GOautodial 4.0 - Persistent Cross-Site Scripting

> Authenticated agents can inject persistent XSS via message subjects, allowing attackers to steal admin session cookies or execute client-side attacks.

- **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:** No
- **Published:** 29 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-5hrw-hqfm-rrvx

## What is CVE-2020-37018?

CVE-2020-37018 is a medium-severity cross-site scripting vulnerability in GOautodial, published on 29 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

GOautodial 4.0 contains a persistent cross-site scripting vulnerability that allows authenticated agents to inject malicious scripts through message subjects. Attackers can craft messages with embedded JavaScript that will execute when an administrator reads the message, potentially stealing session cookies or executing client-side attacks.

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

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


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

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

## Is CVE-2020-37018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37018 is a medium-severity cross-site scripting vulnerability in GOautodial, published on 29 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-37018 exists.

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

## Sources

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

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