# CVE-2026-70382: Stored Cross-Site Scripting in Web Interface


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-fpcw-xmfj-qj6q

## What is CVE-2026-70382?

CVE-2026-70382 is a medium-severity vulnerability in WolfVision Cynap Pro, Cynap Core Pro, Cynap Receiver, Cynap Pure, Cynap Pure Mini, Cynap Pure Pro, published on 26 Oct 2026. 

### Official description

Some externally supplied values stored by the device may be rendered in the web interface without sufficient output encoding. An attacker who can influence one of these values could cause script execution in the browser of a user who views an affected page. Exploitation requires an attacker to influence a stored value and a user to view a page that renders it.

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

## Which versions are affected by CVE-2026-70382?


## How do I fix CVE-2026-70382?

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

## Is CVE-2026-70382 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70382 and fix it if it is affected.

What it is: CVE-2026-70382 is a medium-severity vulnerability in WolfVision Cynap Pro, Cynap Core Pro, Cynap Receiver, Cynap Pure, Cynap Pure Mini, Cynap Pure Pro, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-70382 in the wild and no public exploit code.

Affected product: WolfVision Cynap Pro, Cynap Core Pro, Cynap Receiver, Cynap Pure, Cynap Pure Mini, Cynap Pure Pro. 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-2026-70382/ (Markdown: https://insights.sbomify.com/CVE-2026-70382/index.md)
```

## Sources

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

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