# CVE-2021-37386: Cross-site scripting in n/a

> An attacker can inject HTML via the serial number update function in Furukawa Electric LatAm devices, potentially executing scripts or bypassing security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2023
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-jjh9-589p-ccp8

## What is CVE-2021-37386?

CVE-2021-37386 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Jul 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Furukawa Electric LatAm 423-41W/AC before v1.1.4 and LD421-21W before v1.3.3 were discovered to contain an HTML injection vulnerability via the serial number update function.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2021-37386?

It affects 4 products.


Products: Furukawa 423-41w\/Ac Firmware, Furukawa Ld420-10r Firmware, Furukawa Ld421-21w Firmware, Furukawa Ld421-21wv Firmware.

## How do I fix CVE-2021-37386?

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

## Is CVE-2021-37386 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-37384](https://insights.sbomify.com/CVE-2021-37384/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37386 and fix it if it is affected.

What it is: CVE-2021-37386 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Jul 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-37386 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-2021-37386/ (Markdown: https://insights.sbomify.com/CVE-2021-37386/index.md)
```

## Sources

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

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