# CVE-2026-92257: Netcore NR255-V 1.5.130703 Stored Cross-Site Scripting in L7 Content Management via eval() Sinks

> Attackers can inject persistent scripts into Netcore NR255-V routers via L7 content management, leading to code execution in other users' browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA: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:** 15 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-g4f4-vmp7-9gv7

## What is CVE-2026-92257?

CVE-2026-92257 is a medium-severity cross-site scripting vulnerability in Netcore NR255-V, published on 15 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Netcore NR255-V version 1.5.130703 contains a stored cross-site scripting vulnerability in L7 content management pages that use eval() sinks, affecting the call board text and policy group handling components. Attackers can inject persistent script payloads through these pages to have malicious code executed in the context of other users viewing the affected content.

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

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


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

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

## Is CVE-2026-92257 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92257 is a medium-severity cross-site scripting vulnerability in Netcore NR255-V, published on 15 Sep 2026. 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-2026-92257 in the wild and no public exploit code.

Affected product: Netcore NR255-V. 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-92257/ (Markdown: https://insights.sbomify.com/CVE-2026-92257/index.md)
```

## Sources

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

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