CVE-2025-4365
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 · uneditedArbitrary file read in NetScaler Console and NetScaler SDX (SVM)
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 confidenceThis is an arbitrary file read vulnerability in NetScaler Console and NetScaler SDX (SVM) that allows authenticated attackers to read arbitrary files from the underlying filesystem, potentially exposing sensitive configuration files, credentials, or other system data.
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= 13.1= 14.1>= 13.1-49.13, < 13.1-58.32>= 14.1-4.42, < 14.1-47.46CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the NetScaler product and versionLog into the NetScaler command-line interface and run 'show version' or 'nsversion' to display the installed build version. For SDX appliances, you may also need to check the SVM version using 'show sdx version' or similar SVM-specific command.Affected if The displayed version matches one of the affected ranges: for Console = 13.1 or = 14.1; for SDX 13.1-49.13 through 13.1-58.32, or 14.1-4.42 through 14.1-47.46.
-
Confirm the product type is affectedDetermine whether the system is NetScaler Console (formerly Citrix ADM) or NetScaler SDX. The CVE affects both products but with different version schemes. Check the product name in the management interface or banner.Affected if The product is Citrix NetScaler Console version 13.1 or 14.1, or Citrix NetScaler SDX with a version in the affected ranges listed above.
-
Verify if management interface is network-accessibleCheck network accessibility of the management interface (typically ports 443 or 80) from untrusted networks. This can be done by attempting to reach the management IP from an external location or reviewing firewall rules that permit access to management ports.Affected if The management interface is reachable from networks that are not explicitly trusted, increasing the attack surface for this authenticated vulnerability.
-
Check authentication configurationReview the authentication settings for the management interface to confirm whether local or external authentication (such as LDAP or RADIUS) is properly configured and enforced.Affected if Authentication is not enforced, weak credentials exist, or the default admin account is still in use with default credentials - since this vulnerability requires an authenticated attacker.
You are affected if you are running NetScaler Console 13.1 or 14.1, or NetScaler SDX with a version between 13.1-49.13 and 13.1-58.32 or between 14.1-4.42 and 14.1-47.46, and the management interface is accessible to an attacker who could obtain valid credentials.
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 · scoped13.1-58.3214.1-47.46
Apply the vendor patch or upgrade to a patched version of NetScaler Console or NetScaler SDX. If patching is not immediately possible, restrict network access to the management interfaces and ensure strong authentication is enforced.
NetScaler SDX: 13.1-58.32 or later, 14.1-47.46 or later; NetScaler Console: 13.1-58.32 or later, 14.1-47.46 or later
- 1. Identify the currently installed NetScaler Console or SDX version by navigating to the system administration or diagnostics section.
- 2. For NetScaler SDX 13.1: Plan upgrade to version 13.1-58.32 or later.
- 3. For NetScaler SDX 14.1: Plan upgrade to version 14.1-47.46 or later.
- 4. For NetScaler Console 13.1: Upgrade to version 13.1-58.32 or later.
- 5. For NetScaler Console 14.1: Upgrade to version 14.1-47.46 or later.
- 6. Back up current configuration before performing the upgrade.
- 7. Download the appropriate fixed build from support.citrix.com.
- 8. Apply the upgrade following Citrix standard upgrade procedures for the respective platform.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4365 — 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-4365 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