# CVE-2023-51748: Security feature bypass in n/a

> Attackers can bypass kiosk restrictions in ScaleFusion by using keyboard shortcuts to launch the file explorer, requiring an upgrade to fix.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-hgx9-j24r-974q

## What is CVE-2023-51748?

CVE-2023-51748 is a high-severity vulnerability in n/a, published on 11 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ScaleFusion 10.5.2 does not properly limit users to the Edge application because Ctrl-O and Ctrl-S can be used. This is fixed in 10.5.7 by preventing the launching of the file explorer in Agent-based Multi-App and Single App Kiosk mode.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2023-51748?

It affects 1 product.


Products: Scalefusion Scalefusion.

## How do I fix CVE-2023-51748?

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

## Is CVE-2023-51748 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51748 exists.

## Other vulnerabilities in n/a

- [CVE-2023-50159](https://insights.sbomify.com/CVE-2023-50159/): Security feature bypass in n/a (high 8.8)
- [CVE-2023-51749](https://insights.sbomify.com/CVE-2023-51749/): Security feature bypass in n/a (high 8.8)
- [CVE-2023-51751](https://insights.sbomify.com/CVE-2023-51751/): ScaleFusion 10.5.2 does not properly limit users to the Edge application because Alt-F4 can be used. (high 7.3)
- [CVE-2023-51750](https://insights.sbomify.com/CVE-2023-51750/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51748 and fix it if it is affected.

What it is: CVE-2023-51748 is a high-severity vulnerability in n/a, published on 11 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51748 exists.

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-2023-51748/ (Markdown: https://insights.sbomify.com/CVE-2023-51748/index.md)
```

## Sources

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

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