# CVE-2025-1145: NetVision Information ISOinsight - Reflected Cross-site Scripting

> Unauthenticated attackers can execute arbitrary JavaScript in user browsers via reflected XSS, potentially leading to session hijacking or data theft.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 11 Feb 2025
- **Updated:** 18 Feb 2025

## What is CVE-2025-1145?

CVE-2025-1145 is a medium-severity cross-site scripting vulnerability in NetVision Information ISOinsight, published on 11 Feb 2025. 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

NetVision Information ISOinsight has a Reflected Cross-site Scripting vulnerability, allowing unauthenticated remote attackers to execute arbitrary JavaScript code in the user's browser through phishing techniques.

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

## Which versions are affected by CVE-2025-1145?


## How do I fix CVE-2025-1145?

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

## Is CVE-2025-1145 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1145 and fix it if it is affected.

What it is: CVE-2025-1145 is a medium-severity cross-site scripting vulnerability in NetVision Information ISOinsight, published on 11 Feb 2025. 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-2025-1145 in the wild and no public exploit code.

Affected product: NetVision Information ISOinsight. 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-2025-1145/ (Markdown: https://insights.sbomify.com/CVE-2025-1145/index.md)
```

## Sources

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

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