Secure Access ClientApplication · Citrix

CVE-2025-0320

HIGH · 7.8 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 25.5.1.15 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Local Privilege escalation allows a low-privileged user to gain SYSTEM privileges in Citrix Secure Access Client 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 confidence

Local privilege escalation vulnerability in Citrix Secure Access Client for Windows allows an authenticated low-privileged user to gain SYSTEM-level privileges on the affected system.

MitigationApply the vendor-provided security update or patch for Citrix Secure Access Client for Windows to remediate the privilege escalation vulnerability.

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
Secure Access ClientApplication
Affected:< 25.5.1.15

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
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 checks

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

  1. Verify Citrix Secure Access Client is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for Citrix Secure Access Client in the installed programs list
    Affected if The program is not listed or not found on the system, then the vulnerability does not apply
  2. Identify the installed version number
    Right-click on the Citrix Secure Access Client application in Programs and Features and select Properties, or locate the executable in the installation directory and view its file properties to find the version
    Affected if Unable to determine the version number from the installed software
  3. Compare installed version against affected range
    Compare the installed version number (for example, 25.5.0.0 or 25.4.0.0) to the affected range: any version prior to 25.5.1.15 is vulnerable
    Affected if The installed version is lower than 25.5.1.15 (for example, 25.5.1.14, 25.5.0.0, or any earlier version)
  4. Confirm the client is in use or enabled
    Check if the Citrix Secure Access Client service is running or if the client application is actively used on the system by viewing running services or recently accessed programs
    Affected if The client is actively installed and running, making the privilege escalation vulnerability exploitable

A user is affected if Citrix Secure Access Client for Windows is installed with a version number lower than 25.5.1.15.

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
Upgrade available Upgrade to 25.5.1.15 or later
Fixed in 25.5.1.15
Interim mitigation

Apply the vendor-provided security update or patch for Citrix Secure Access Client for Windows to remediate the privilege escalation vulnerability.

Recommended fix High confidence

Citrix Secure Access Client version 25.5.1.15 or later

  1. 1. Verify the current version of Citrix Secure Access Client installed on the system by checking Add/Remove Programs or the application's About section
  2. 2. Navigate to Citrix support portal (support.citrix.com) and locate the download page for Citrix Secure Access Client version 25.5.1.15 or later
  3. 3. Download the appropriate installer for your Windows version (x64 or x86)
  4. 4. Run the installer with administrator privileges to apply the update
  5. 5. Restart the system if prompted by the installer
  6. 6. Verify the installed version is 25.5.1.15 or higher after the update completes
Caveat Standard client upgrade; ensure compatibility with your Citrix gateway/SSO infrastructure before deployment in production environments

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

Fix this in Secure Access Client Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0320 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0320 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