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

> Attackers can exploit CSRF in the Usb_upload.htm component to send crafted requests, potentially modifying data or bypassing security controls.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 13 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** GHSA-h3vx-8rv6-2h7x

## What is CVE-2022-41489?

CVE-2022-41489 is a high-severity vulnerability in n/a, published on 13 Oct 2022. 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

WAYOS LQ_09 22.03.17V was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to send crafted requests to the server from the affected device. This vulnerability is exploitable due to a lack of authentication in the component Usb_upload.htm.

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

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

It affects 6 products.


Products: Wayos Lq-04 Firmware, Wayos Lq-05 Firmware, Wayos Lq-06 Firmware, Wayos Lq-07 Firmware, Wayos Lq-08 Firmware, Wayos Lq-09 Firmware.

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

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

## Is CVE-2022-41489 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41489 is a high-severity vulnerability in n/a, published on 13 Oct 2022. 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-2022-41489 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-41489/ (Markdown: https://insights.sbomify.com/CVE-2022-41489/index.md)
```

## Sources

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

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