# CVE-2020-16256: The API on Winston 1.5.4 devices is vulnerable to CSRF.


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xx9g-fvg8-hmfw

## What is CVE-2020-16256?

CVE-2020-16256 is a high-severity vulnerability in n/a, published on 28 Oct 2020. 

### Official description

The API on Winston 1.5.4 devices is vulnerable to CSRF.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Winstonprivacy Winston Firmware.

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

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

## Is CVE-2020-16256 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-16257](https://insights.sbomify.com/CVE-2020-16257/): Winston 1.5.4 devices are vulnerable to command injection via the API. (critical 9.8)
- [CVE-2020-16259](https://insights.sbomify.com/CVE-2020-16259/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-16263](https://insights.sbomify.com/CVE-2020-16263/): Winston 1.5.4 devices have a CORS configuration that trusts arbitrary origins. (critical 9.1)
- [CVE-2020-16262](https://insights.sbomify.com/CVE-2020-16262/): Winston 1.5.4 devices have a local www-data user that is overly permissioned, resulting in root privilege escalation. (high 7.8)
- [CVE-2020-16260](https://insights.sbomify.com/CVE-2020-16260/): Winston 1.5.4 devices do not enforce authorization. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-16256 is a high-severity vulnerability in n/a, published on 28 Oct 2020. 
Exploitation: There is no known exploitation of CVE-2020-16256 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-2020-16256/ (Markdown: https://insights.sbomify.com/CVE-2020-16256/index.md)
```

## Sources

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

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