dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-45313

HIGH · 7.7 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
No privileges 5 weeks old

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 · unedited
Sandboxie-Plus is an open source sandbox-based isolation software for Windows. Prior to 1.17.6, GuiServer::WndHookRegisterSlave in Sandboxie/core/svc/GuiServer.cpp stores attacker-supplied hthread and hproc fields from a GUI_WND_HOOK_REGISTER request without validating that the thread belongs to the sandboxed process or that the function pointer is in the caller address space, and GuiServer::WndHookNotifySlave then calls OpenThread(THREAD_SET_CONTEXT, FALSE, whk->hthread) and QueueUserAPC((PAPCFUNC)whk->hproc, hThread, (ULONG_PTR)req->threadid) as SYSTEM, allowing a sandboxed process to execute arbitrary code in an unsandboxed host process. This issue is fixed in version 1.17.6.

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 · high confidence

In GuiServer::WndHookRegisterSlave, the code stores attacker-supplied hthread and hproc fields from GUI_WND_HOOK_REGISTER requests without validating that the thread belongs to the sandboxed process or that the function pointer is in the caller address space. GuiServer::WndHookNotifySlave then calls OpenThread and QueueUserAPC with these attacker-controlled values as SYSTEM, enabling a sandboxed process to escape isolation and execute arbitrary code in an unsandboxed host process.

MitigationUpgrade to Sandboxie-Plus version 1.17.6 or later which contains the fix for the missing validation in GuiServer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Sandboxie version
    Open Windows Control Panel > Programs and Features, or check the executable properties of the Sandboxie installation (typically in C:\Program Files\Sandboxie-Plus or C:\Program Files\Sandboxie). Right-click the main executable and view Properties > Details to see the File Version.
    Affected if The installed version is below 1.17.6 (the fixed release)
  2. Locate the GuiServer component
    The GuiServer component is part of the core Sandboxie installation. Check for SbieSvc.exe or GuiServer.exe in the Sandboxie installation directory (typically C:\Program Files\Sandboxie-Plus\ or C:\Program Files\Sandboxie\).
    Affected if The GuiServer component exists and is running as part of the Sandboxie installation
  3. Confirm GUI window hooks are in use
    The vulnerability is triggered via GUI_WND_HOOK_REGISTER requests. Monitor for processes creating window hooks or using the SbieWnd hook mechanism. Check Sandboxie logs (typically in %APPDATA%\Sandboxie-Plus\Logs\ or the sandboxed application's data folder) for any GUI_WND_HOOK_REGISTER activity.
    Affected if The sandboxed environment is actively using GUI window hooks that communicate with GuiServer
  4. Check process privileges
    The vulnerability allows a sandboxed process to execute code as SYSTEM. Review running processes under the Sandboxie sandbox to identify any processes running with elevated or SYSTEM privileges that should not have them.
    Affected if A sandboxed process has achieved execution as SYSTEM or escaped the sandbox isolation

A user is affected if running any Sandboxie-Plus version below 1.17.6 that has the GuiServer component active and GUI window hooks are being used by sandboxed applications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Sandboxie-Plus version 1.17.6 or later which contains the fix for the missing validation in GuiServer.

Recommended fix High confidence

Upgrade to Sandboxie-Plus version 1.17.6 or later

  1. Navigate to the official Sandboxie-Plus GitHub releases page at github.com/sandboxie-plus/Sandboxie
  2. Locate and download version 1.17.6 (or the latest version if 1.17.6 is no longer available)
  3. Close any running Sandboxie-Plus applications
  4. Run the installer and follow the prompts to upgrade the installation
  5. Restart any Sandboxie-Plus services if prompted
  6. Verify the installation by checking the version number in the application About section

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45313 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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