CVE-2023-51751
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedScaleFusion 10.5.2 does not properly limit users to the Edge application because Alt-F4 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceScaleFusion 10.5.2's kiosk mode (both Agent-based Multi-App and Single App) can be bypassed by pressing Alt-F4, which closes the Edge application and launches the Windows file explorer. This breaks the intended lockdown and allows users to access system functions outside the controlled Edge application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.5.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ScaleFusion versionOpen ScaleFusion Agent or check the installed package version on the managed Windows device. Look in Programs and Features or the ScaleFusion Agent UI for the version number.Affected if The installed version is exactly 10.5.2
-
Confirm kiosk mode is activeCheck if ScaleFusion kiosk mode (Multi-App or Single App) is enabled and currently enforcing lockdown on the Windows device. Verify the profile applied to the device includes kiosk settings.Affected if Kiosk mode is enabled and the device is in a locked-down kiosk state
-
Test Alt-F4 bypass vulnerabilityWhile in ScaleFusion kiosk mode running Edge, press Alt-F4 on the keyboard. Observe whether Edge application closes and Windows File Explorer launches.Affected if Pressing Alt-F4 closes Edge and opens File Explorer, bypassing the kiosk lockdown
A user is affected if ScaleFusion version 10.5.2 is installed with kiosk mode enabled and the Alt-F4 key combination can escape the Edge kiosk to open File Explorer.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade ScaleFusion to version 10.5.7 or later, which prevents the file explorer from launching in kiosk mode.
Upgrade from ScaleFusion 10.5.2 to version 10.5.7 or later
- Obtain ScaleFusion version 10.5.7 or later from the official ScaleFusion download portal or update mechanism
- Apply the upgrade following ScaleFusion's standard software update procedure for the MDM agent
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-51751 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data