# CVE-2020-8193: Citrix ADC, Gateway, and SD-WAN WANOP Appliance Authorization Bypass

> Unauthenticated attackers can access restricted URL endpoints in Citrix ADC and Gateway products due to improper access control.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-wrxp-682m-vm9p

## What is CVE-2020-8193?

CVE-2020-8193 is a medium-severity missing authorization vulnerability in Citrix ADC, Citrix Gateway, Citrix SDWAN WAN-OP, published on 10 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper access control 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 unauthenticated access to certain URL endpoints.

Weakness: CWE-287 (Improper Authentication), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2020-8193?

It affects 4 products.


Products: Citrix Application Delivery Controller Firmware, Citrix Gateway Firmware, Citrix Netscaler Gateway Firmware, Citrix Sd-Wan Wanop.

## How do I fix CVE-2020-8193?

No fix has been published for CVE-2020-8193 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-8193 being exploited?

Yes. Attackers have exploited CVE-2020-8193 in the wild since at least 3 Nov 2021.

Public exploit code:

- Citrix ADC Vulns (github_poc): https://github.com/jas502n/CVE-2020-8193
- Citrix ADC从权限绕过到RCE (github_poc): https://github.com/Airboi/Citrix-ADC-RCE-CVE-2020-8193
- Scanning for CVE-2020-8193 - Auth Bypass check (github_poc): https://github.com/PR3R00T/CVE-2020-8193-Citrix-Scanner
- This Metasploit-Framework module can be use to help companies to check the last Citrix vulnerability CVE-2020-8193, CVE-2020-8195 and CVE-2020-8196 (disclosed July 08, 2020). (github_poc): https://github.com/Zeop-CyberSec/citrix_adc_netscaler_lfi
- https://github.com/ctlyz123/CVE-2020-8193 (github_poc): https://github.com/ctlyz123/CVE-2020-8193
- Citrix - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-8193.yaml

## Other vulnerabilities in Citrix ADC, Citrix Gateway, Citrix SDWAN WAN-OP

- [CVE-2022-27518](https://insights.sbomify.com/CVE-2022-27518/): Citrix Application Delivery Controller (ADC) and Gateway Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-19781](https://insights.sbomify.com/CVE-2019-19781/): Citrix ADC, Gateway, and SD-WAN WANOP Appliance Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-8195](https://insights.sbomify.com/CVE-2020-8195/): Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure (medium 6.5, exploited in the wild)
- [CVE-2020-8196](https://insights.sbomify.com/CVE-2020-8196/): Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure (medium 4.3, exploited in the wild)
- [CVE-2022-27510](https://insights.sbomify.com/CVE-2022-27510/): Unauthorized access to Gateway user capabilities (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8193 and fix it if it is affected.

What it is: CVE-2020-8193 is a medium-severity missing authorization vulnerability in Citrix ADC, Citrix Gateway, Citrix SDWAN WAN-OP, published on 10 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-8193 in the wild since at least 3 Nov 2021.

Affected product: Citrix ADC, Citrix Gateway, Citrix SDWAN WAN-OP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-8193/ (Markdown: https://insights.sbomify.com/CVE-2020-8193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8193
- OSV: https://osv.dev/vulnerability/CVE-2020-8193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-8193/
Summaries are generated and may contain mistakes; the official description above is the record.