# CVE-2025-48396: File upload in Eaton Brightlayer Software Suite (BLSS)

> Attackers can execute arbitrary code via improper file upload validation in Eaton Brightlayer Software Suite.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-3424-mxvj-pcgx

## What is CVE-2025-48396?

CVE-2025-48396 is a high-severity vulnerability in Eaton Brightlayer Software Suite (BLSS), published on 3 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Arbitrary code execution is possible due to improper validation of the file upload functionality in Eaton BLSS. This security issue has been fixed in the latest script patch latest version of of Eaton BLSS (7.3.0.SCP004).

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-48396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48396 is a high-severity vulnerability in Eaton Brightlayer Software Suite (BLSS), published on 3 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48396 in the wild and no public exploit code.

Affected product: Eaton Brightlayer Software Suite (BLSS). 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-48396/ (Markdown: https://insights.sbomify.com/CVE-2025-48396/index.md)
```

## Sources

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

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