# CVE-2025-46749: Improper Neutralization of Input

> Authenticated users can inject scripts into unsanitized fields, leading to client-side script execution in SEL Blueframe OS.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **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:** 12 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-fr65-4fvj-c9rf

## What is CVE-2025-46749?

CVE-2025-46749 is a medium-severity cross-site scripting vulnerability in Schweitzer Engineering Laboratories SEL Blueframe OS, published on 12 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An authenticated user could submit scripting to fields that lack proper input and output sanitization leading to subsequent client-side script execution.

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

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


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

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

## Is CVE-2025-46749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46749 is a medium-severity cross-site scripting vulnerability in Schweitzer Engineering Laboratories SEL Blueframe OS, published on 12 May 2025. 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-2025-46749 in the wild and no public exploit code.

Affected product: Schweitzer Engineering Laboratories SEL Blueframe OS. 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-46749/ (Markdown: https://insights.sbomify.com/CVE-2025-46749/index.md)
```

## Sources

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

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