# CVE-2025-63226: Auth bypass in n/a

> Attackers on the same network can hijack sessions to bypass authentication and add new users on the Sencore SMP100 media platform.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-32fr-75xx-54f3

## What is CVE-2025-63226?

CVE-2025-63226 is a medium-severity authentication bypass vulnerability in n/a, published on 18 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Sencore SMP100 SMP Media Platform (firmware versions V4.2.160, V60.1.4, V60.1.29) is vulnerable to session hijacking due to improper session management on the /UserManagement.html endpoint. Attackers who are on the same network as the victim and have access to the target's logged-in session can access the endpoint and add new users without any authentication. This allows attackers to gain unauthorized access to the system and perform malicious activities.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 3 products.


Products: Sencore Decoder-Ccv2 Firmware, Sencore En2sdi-2hd Firmware, Sencore Smp100 Firmware.

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

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

## Is CVE-2025-63226 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63226 is a medium-severity authentication bypass vulnerability in n/a, published on 18 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-63226 in the wild and no public exploit code.

Affected product: n/a. 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-63226/ (Markdown: https://insights.sbomify.com/CVE-2025-63226/index.md)
```

## Sources

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

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