Netscaler Application Delivery ControllerApplication · Citrix
CVE-2025-5349
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 · uneditedImproper access control on the NetScaler Management Interface in NetScaler ADC and NetScaler Gateway
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 confidenceImproper access control on the NetScaler Management Interface in NetScaler ADC and NetScaler Gateway allows authenticated users to perform unauthorized actions or access sensitive management functions beyond their intended privileges, likely due to insufficient authorization checks in the management API.
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
Netscaler Application Delivery ControllerApplication
>= 12.1, < 12.1-55.328>= 13.1, < 13.1-37.235>= 13.1, < 13.1-58.32>= 14.1, < 14.1-43.56
Netscaler GatewayApplication
>= 13.1, < 13.1-58.32>= 14.1, < 14.1-43.56CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 NetScaler product and versionRun 'show version' or 'nsversion' command on the NetScaler CLI to determine if the device is NetScaler ADC or NetScaler Gateway and its exact firmware versionAffected if The version falls within any of the affected ranges: ADC 12.1 before 12.1-55.328, ADC 13.1 before 13.1-37.235 or before 13.1-58.32, ADC 14.1 before 14.1-43.56, Gateway 13.1 before 13.1-58.32, or Gateway 14.1 before 14.1-43.56
-
Verify management interface accessibilityConfirm the NetScaler Management Interface (typically ports 443 or 8443) is exposed to network segments beyond trusted management networks; check ns.conf for 'set ns mgmt-port' settings and review firewall rules or ACLs protecting the management IPAffected if The management interface is accessible from untrusted networks or the internet rather than being restricted to trusted management subnets only
-
Review user account privilegesUse 'show system user' or access the management GUI under Configuration > User Administration > Users to list all configured administrative accounts and their assigned rolesAffected if There exist non-administrative users or service accounts with limited roles that could potentially gain elevated privileges through the management API unauthorized actions
-
Check RBAC role assignmentsNavigate to Configuration > User Administration > RBAC > Roles or use 'show rbac role' command to inspect the specific permissions granted to each user roleAffected if Users are assigned roles that do not properly restrict access to sensitive management functions, allowing privilege escalation beyond the intended role scope
A user is affected if the NetScaler is running a version within the affected ranges AND the management interface is accessible to authenticated users with insufficiently scoped privileges.
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 · scoped12.1-55.32813.1-37.23513.1-58.32
Restrict network access to the NetScaler Management Interface to trusted management networks only, and apply vendor-provided patches when available; implement role-based access control (RBAC) policies following least-privilege principles.
Upgrade to NetScaler ADC 12.1-55.328, 13.1-37.235, 13.1-58.32, or 14.1-43.56 (and NetScaler Gateway 13.1-58.32 or 14.1-43.56) based on your current release branch
- 1. Identify current NetScaler ADC or Gateway version by running 'show version' or checking the management interface
- 2. Create a complete configuration backup using 'save ns config' and export via the management interface
- 3. Test the upgrade in a non-production environment first to validate compatibility
- 4. Schedule maintenance window as upgrade requires system restart
- 5. Download the appropriate fixed build from Citrix download portal (support.citrix.com): 12.1-55.328, 13.1-37.235, 13.1-58.32, or 14.1-43.56
- 6. Upload the firmware via the management interface or using 'install' command in the shell
- 7. Reboot the appliance using 'reboot' command
- 8. After reboot, verify new version with 'show version' and confirm management interface is accessible
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Netscaler Application Delivery Controller
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5349 — 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-5349 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