# CVE-2020-8282: Cross-site request forgery in EdgePower

> Missing CSRF protections in EdgePower firmware allow attackers to perform unauthorized remote code execution.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-89jc-hqfc-w5xg

## What is CVE-2020-8282?

CVE-2020-8282 is a high-severity vulnerability in EdgePower, published on 14 Dec 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

A security issue was found in EdgePower 24V/54V firmware v1.7.0 and earlier where, due to missing CSRF protections, an attacker would have been able to perform unauthorized remote code execution.

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

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

It affects 2 products.


Products: Ui Edgemax Edgepower 24v Firmware, Ui Edgemax Edgepower 54v Firmware.

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

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

## Is CVE-2020-8282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8282 is a high-severity vulnerability in EdgePower, published on 14 Dec 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-2020-8282 in the wild and no public exploit code.

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

## Sources

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

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