# CVE-2020-37278: Weaver e-Bridge Unauthenticated Arbitrary File Read via saveYZJFile

> Remote attackers can read arbitrary files and perform server-side request forgery via the saveYZJFile endpoint in Weaver e-Bridge.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-jh67-5hqg-r8p4

## What is CVE-2020-37278?

CVE-2020-37278 is a high-severity server-side request forgery vulnerability in Weaver e-Bridge, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Weaver e-Bridge contains an unauthenticated arbitrary file read vulnerability that allows remote attackers to access arbitrary files on the host system by supplying a file: URL to the downloadUrl parameter of the saveYZJFile endpoint. Attackers can exploit this flaw to read sensitive files such as /etc/passwd or configuration and credential files, and the same endpoint's support for http(s) URLs also enables server-side request forgery against internal network resources. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-17.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2020-37278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37278 is a high-severity server-side request forgery vulnerability in Weaver e-Bridge, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-37278 in the wild and no public exploit code.

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

## Sources

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

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