dbcve.org
Netscaler Application Delivery ControllerApplication · Citrix

CVE-2023-3466

MEDIUM · 6.1 CVSS v3.1 Developing Published 2023-07-19
Fix available
A fix is available. Upgrade to 12.1-55.297 / 13.0-91.13 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected Cross-Site Scripting (XSS)

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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
Affected:>= 12.1, < 12.1-55.297>= 13.0, < 13.0-91.13>= 13.1, < 13.1-37.159>= 13.1, < 13.1-49.13= 11.1-65.22
Netscaler GatewayApplication
Affected:>= 13.0, < 13.0-91.13>= 13.1, < 13.1-49.13

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 12.1-55.297 / 13.0-91.13 / 13.1-37.159 or later
Fixed in 12.1-55.29713.0-91.1313.1-37.159
Recommended fix High confidence

Netscaler ADC 12.1-55.297, 13.0-91.13, or 13.1-49.13; Netscaler Gateway 13.0-91.13 or 13.1-49.13

  1. 1. Back up the current Netscaler configuration using the command 'save ns config' and download the backup file.
  2. 2. Download the appropriate Citrix Netscaler build for your version branch from support.citrix.com (12.1-55.297, 13.0-91.13, or 13.1-49.13).
  3. 3. Upload the new firmware build to the Netscaler using the web interface (System > Firmware) or via SCP.
  4. 4. Install the new firmware using the command 'install ns firmware <firmware_file>' or through the web interface.
  5. 5. Reboot the Netscaler appliance using 'reboot' command.
  6. 6. After reboot, verify the new version is running using 'show ns version' and confirm the build matches the fixed release.
  7. 7. Verify the configuration is intact and test critical application functionality.
Caveat Review Citrix release notes for any configuration changes or deprecated features between your current version and the target fixed version before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3466 — 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-2023-3466 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