# CVE-2022-45228: Cross-site request forgery in n/a

> An attacker can force a logged-in user to log out via a Cross-Site Request Forgery vulnerability in the Dragino LoRa LG01 gateway.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A: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:** 12 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-743q-wpgm-76xq

## What is CVE-2022-45228?

CVE-2022-45228 is a low-severity vulnerability in n/a, published on 12 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Dragino Lora LG01 18ed40 IoT v4.3.4 was discovered to contain a Cross-Site Request Forgery in the logout page.

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

## Which versions are affected by CVE-2022-45228?

It affects 1 product.


Products: Dragino Lg01 Lora Firmware.

## How do I fix CVE-2022-45228?

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

## Is CVE-2022-45228 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45227](https://insights.sbomify.com/CVE-2022-45227/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45228 and fix it if it is affected.

What it is: CVE-2022-45228 is a low-severity vulnerability in n/a, published on 12 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-45228 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-2022-45228/ (Markdown: https://insights.sbomify.com/CVE-2022-45228/index.md)
```

## Sources

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

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