CVE-2025-4879
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 · uneditedLocal Privilege escalation allows a low-privileged user to gain SYSTEM privileges in Citrix Workspace app for Windows
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 confidenceCVE-2025-4879 is a local privilege escalation vulnerability in Citrix Workspace app for Windows that allows an authenticated low-privileged user to elevate their privileges to SYSTEM level. The vulnerability stems from improper privilege management within the application, enabling a local attacker to escalate beyond their assigned user context.
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< 2402< 2409= 2402CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Citrix Workspace is installedCheck the installed programs list via Control Panel > Programs and Features, or run: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Citrix*Workspace*'}Affected if Citrix Workspace app for Windows is present on the system
-
Determine the installed version numberRun: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Citrix*Workspace*'} | Select-Object Name, Version. Alternatively, check the Windows Registry at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductID} for the DisplayVersion value.Affected if The displayed version number is less than 2409 (for example, 2402, 2408, 2312, etc.)
-
Confirm the Citrix Workspace service existsOpen Services (services.msc) and look for services named 'Citrix Workspace' or 'Citrix HDX 3D Pro', or run: Get-Service | Where-Object {$_.DisplayName -like '*Citrix*'}Affected if A Citrix Workspace service is present and running on the system
-
Check if low-privileged user context can interact with Citrix serviceUsing the system, verify you are running as a standard (non-admin) user. Run: whoami /groups | findstr -i "BUILTIN\\Users". Confirm the Citrix service runs under a higher-privileged account (viewable in Service Properties > Log On tab).Affected if The system has a standard user account AND the Citrix Workspace service runs under SYSTEM or Administrator account
-
Verify the vulnerable privilege assignment existsInspect Citrix Workspace installation directory (typically C:\Program Files\Citrix\Citrix Workspace\) for any scheduled tasks or configurations that grant elevated privileges to user-accessible binaries. Run: Get-Acl -Path "C:\Program Files\Citrix\Citrix Workspace\*" | Select-Object OwnerAffected if Non-admin users have write or execute permissions to Citrix binaries that run with elevated privileges
A system is affected if Citrix Workspace app for Windows version 2408 or earlier (less than 2409) is installed AND a low-privileged local user account exists on the machine.
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 · scoped24022409
Apply the vendor-supplied patch for Citrix Workspace app when available. In the interim, limit local user permissions and monitor for suspicious processes spawning from the Citrix Workspace service.
2409 or later (Citrix Workspace for Windows)
- Identify the currently installed Citrix Workspace version from Add/Remove Programs or the app's About section
- Download the latest Citrix Workspace version from official Citrix sources (citrix.com/downloads)
- Close all running Citrix Workspace processes via Task Manager
- Run the Workspace installer with administrator privileges
- Follow the on-screen installation prompts, selecting 'Repair' or 'Upgrade' option
- Restart the system after installation completes
- Verify the new version is installed and the application launches correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4879 — 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-2025-4879 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