CVE-2020-8191
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 input validation in Citrix ADC and Citrix Gateway versions before 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14 and 10.5-70.18 and Citrix SDWAN WAN-OP versions before 11.1.1a, 11.0.3d and 10.2.7 allows 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 · high confidenceImproper input validation in Citrix ADC and Citrix Gateway (and SDWAN WAN-OP) allows reflected Cross Site Scripting (XSS). The vulnerability stems from unsanitized user input being reflected back in web responses without proper encoding, enabling attackers to inject malicious scripts into legitimate web pages.
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>= 10.5, < 10.5-70.18>= 11.1, < 11.1-64.14>= 12.0, < 12.0-63.21>= 12.1, < 12.1-57.18>= 13.0, < 13.0-58.30>= 10.5, < 10.5-70.18>= 11.1, < 11.1-64.14>= 12.0, < 12.0-63.21>= 12.1, < 12.1-57.18>= 13.0, < 13.0-58.30>= 10.2, < 10.2.7>= 11.0, < 11.0.3d>= 11.1, < 11.1.1aCVSS 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
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 Citrix ADC firmware versionAccess the command line interface and run 'show version' or log into the web UI and check System > Information > Version. For CLI: `show ns version`Affected if The installed version falls within any of these ranges: 10.5 to 10.5-70.17, 11.1 to 11.1-64.13, 12.0 to 12.0-63.20, 12.1 to 12.1-57.17, 13.0 to 13.0-58.29
-
Identify the Citrix Netscaler Gateway firmware versionRun `show version` at the command prompt or check the web UI under Configuration > System > InformationAffected if The installed version falls within any of these ranges: 10.5 to 10.5-70.17, 11.1 to 11.1-64.13, 12.0 to 12.0-63.20, 12.1 to 12.1-57.17
-
Identify the Citrix Gateway Firmware versionRun `show version` or access the web interface and navigate to the firmware version information pageAffected if The installed version is between 13.0 and 13.0-58.29 (inclusive)
-
Identify the Citrix SDWAN WAN-OP firmware versionAccess the SDWAN web UI or use the CLI command to display the firmware version, typically found under Administration > Device SettingsAffected if The installed version falls within any of these ranges: 10.2 to 10.2.6, 11.0 to 11.0.3c, 11.1 to 11.1.1
-
Verify the web management interface is accessibleAttempt to reach the Citrix ADC/Gateway login page over HTTPS on port 443 or the configured management port. Check if the NSGUI or VPN virtual server is enabled and boundAffected if The web interface is exposed and the device is on an affected version - the XSS flaw requires the web UI to be reachable for exploitation
If any Citrix ADC, Netscaler Gateway, Citrix Gateway, or SDWAN WAN-OP installation is running a version lower than the fixed releases (10.5-70.18, 11.1-64.14, 12.0-63.21, 12.1-57.18, 13.0-58.30, or 11.1.1a for SDWAN) and has its web management interface exposed, the environment is affected by this reflected XSS vulnerability.
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.
From vendor data10.2.710.5-70.1811.0.3d
Upgrade Citrix ADC/Gateway to version 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14, or 10.5-70.18 (or later); upgrade SDWAN WAN-OP to 11.1.1a, 11.0.3d, or 10.2.7 (or later). Implement WAF rules as interim control if immediate upgrade is not feasible.
- 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-2020-8191 — 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-2020-8191 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