CVE-2023-3519

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-07-19), indicating real-world exploitation has been confirmed by US federal agencies. It is also listed on ENISA's EU Known Exploited Vulnerabilities catalogue (Source: ENISA EUVD). NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, ENISA's EU Known Exploited Vulnerabilities catalogue, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2023-44176 (ENISA EUVD) · GHSA-m4j4-rmj5-w5gp (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • 1,664 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
  • Linked to ransomware campaigns
CISA-KEV: ExploitedENISA EU KEV: Listed (Source: ENISA EUVD)EPSS PROB: 99.7%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: 1,664

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Citrix Systems, Inc.) lists Citrix NetScaler ADC versions 13.1 up to but not including 49.13, 13.0 up to but not including 91.13, 13.1-FIPS up to but not including 37.159, 12.1-FIPS up to but not including 55.297 and 1 more range; Citrix NetScaler Gateway versions 13.1 up to but not including 49.13 and 13.0 up to but not including 91.13 as affected. No release containing a fix is confirmed on record.

Unauthenticated remote code execution

Internet exposure · derived from Shodan data

1,664 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2023-3519, in our KEV-Exposure radar’s Shodan-derived sample.

across 13 countries (Germany, Australia, United States, United Kingdom, Mauritius)top: netscaler_gateway🔒 ransomware-linked
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
84
EG Risk 84/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
99.7%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and ENISA EU KEV (Source: ENISA EUVD) and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

ENISA EU KEV: listed January 23, 2025, reported by cnw.

Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. How a listing moves the EG score

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://support.citrix.com/article/CTX561482/citrix-adc-and-citrix-gateway-security-bulletin-for-cve20233519-cve20233466-cve20233467 · https://nvd.nist.gov/vuln/detail/CVE-2023-3519

Published

July 19, 2023

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Oct 28, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-3519

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 111× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,028 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 928 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 22:12 UTCEG score recompute
  2. 2026-11-01 22:11 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-31 20:57 UTCEG score recompute
  4. 2026-10-31 20:57 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-30 19:47 UTCEG score recompute
  6. 2026-10-30 19:47 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-29 18:36 UTCEG score recompute
  8. 2026-10-29 18:36 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-28 17:25 UTCEG score recompute
  10. 2026-10-28 17:24 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-27 16:10 UTCEG score recompute
  12. 2026-10-27 16:10 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-26 14:59 UTCEG score recompute
  14. 2026-10-26 14:59 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-25 16:29 UTCEPSS rescoreEPSS 99.7% · 99th percentile
  16. 2026-10-25 13:47 UTCEG score recompute
  17. 2026-10-25 13:47 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-25 13:46 UTCENISA EU KEV listingEUVD-2023-44176 · listed January 23, 2025 · reported by cnw · Source: ENISA EUVD
  19. 2026-10-24 23:36 UTCEG score recompute
  20. 2026-10-24 23:36 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-23 22:26 UTCEG score recompute
  22. 2026-10-23 22:25 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-22 21:14 UTCEG score recompute
  24. 2026-10-22 21:14 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-21 20:03 UTCEG score recompute
Show 75 more
  1. 2026-10-21 20:03 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-20 18:51 UTCEG score recompute
  3. 2026-10-20 18:51 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-19 17:40 UTCEG score recompute
  5. 2026-10-19 17:40 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-18 16:27 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-18 13:29 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-18 07:58 UTCEG score recompute
  9. 2026-10-17 12:17 UTCEG score recompute
  10. 2026-10-17 12:17 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-16 11:04 UTCEG score recompute
  12. 2026-10-16 11:04 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-15 16:29 UTCEPSS rescoreEPSS 99.7% · 99th percentile
  14. 2026-10-15 09:52 UTCEG score recompute
  15. 2026-10-15 09:51 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-14 08:39 UTCEG score recompute
  17. 2026-10-14 08:39 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-13 07:28 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-12 18:24 UTCEG score recompute
  20. 2026-10-12 06:15 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-12 02:30 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-11 22:47 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-11 21:50 UTCEG score recompute
  24. 2026-10-11 19:03 UTCEG score recompute
  25. 2026-10-11 19:03 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-11 15:20 UTCEG score recompute
  27. 2026-10-11 15:20 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-11 11:37 UTCEG score recompute
  29. 2026-10-11 11:37 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-11 07:54 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-11 04:10 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-11 00:27 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-10 20:45 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-10 17:01 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-10 13:19 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-10 09:36 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-10 05:53 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-10 02:09 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-09 22:26 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-09 18:44 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-09 15:01 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-09 11:18 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-09 07:36 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-09 03:53 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-09 00:10 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-08 20:27 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-08 16:44 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-08 13:01 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-08 09:17 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-08 05:34 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-08 01:51 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-07 22:07 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-07 18:23 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-07 14:41 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-07 10:58 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-07 07:15 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-07 03:32 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-06 23:47 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-06 20:04 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-06 16:21 UTCEG score recompute
  61. 2026-10-06 16:21 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-06 15:15 UTCEPSS rescoreEPSS 99.7% · 99th percentile
  63. 2026-10-06 12:39 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-06 08:56 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-06 05:13 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-06 01:27 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-06 01:27 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-05 21:44 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-05 18:01 UTCEG score recompute
  70. 2026-10-05 18:01 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-05 17:41 UTCEPSS rescoreEPSS 99.7% · 99th percentile
  72. 2026-10-05 14:18 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-10-05 10:35 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-05 06:50 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-05 03:07 UTCGHSA enrichmentGHSA-m4j4-rmj5-w5gp · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(10 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 4 GitHub PoCs), as are 1 Nuclei detection template, 4 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitexploit/freebsd/http/citrix_formssso_target_rce✓ verified
    Published Aug 3, 2023

    Citrix ADC (NetScaler) Forms SSO Target RCE

    Open source ↗
  • Nucleihttp/cves/2023/CVE-2023-3519.yaml
    Published Oct 18, 2025

    Citrix NetScaler ADC and NetScaler Gateway - Remote Code Execution

    Open source ↗
  • GitHub PoCdhammerg/CVE-2023-3519
    Published Oct 27, 2023

    Stack-Overflow on Citrix

    Open source ↗
  • GitHub PoCChocapikk/CVE-2023-3519
    Published Aug 24, 2023

    Citrix ADC RCE CVE-2023-3519

    Open source ↗
  • GitHub checkermandiant/citrix-ioc-scanner-cve-2023-3519
    Published Aug 10, 2023
    Open source ↗
  • GitHub checkerSalehLardhi/CVE-2023-3519
    Published Jul 21, 2023

    CVE-2023-3519 vuln for nuclei scanner

    Open source ↗
  • GitHub PoCBishopFox/CVE-2023-3519
    Published Jul 21, 2023

    RCE exploit for CVE-2023-3519

    Open source ↗
  • GitHub PoCmr-r3b00t/CVE-2023-3519
    Published Jul 21, 2023
    Open source ↗
  • GitHub checkersecurekomodo/citrixInspector
    Published Jul 20, 2023

    Accurately fingerprint and detect vulnerable (and patched!) versions of Netscaler / Citrix ADC to CVE-2023-3519

    Open source ↗
  • GitHub checkertelekom-security/cve-2023-3519-citrix-scanner
    Published Jul 20, 2023

    Citrix Scanner for CVE-2023-3519

    Open source ↗

Frequently asked(6)

What is CVE-2023-3519?
CVE-2023-3519 is a critical-severity vulnerability; its CVE record was published on July 19, 2023. Unauthenticated remote code execution
When was the CVE record for CVE-2023-3519 published?
The CVE record for CVE-2023-3519 was published on July 19, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-3519 actively exploited?
Yes. CISA added CVE-2023-3519 to the Known Exploited Vulnerabilities catalog on July 19, 2023, affecting Citrix NetScaler ADC and NetScaler Gateway. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation. ENISA's EU Known Exploited Vulnerabilities catalogue lists CVE-2023-3519 (added January 23, 2025, reported by cnw): ENISA records its exploitation in the wild. Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement.
What is the CVSS score of CVE-2023-3519?
CVE-2023-3519 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2023-3519?
CVE-2023-3519 affects Citrix NetScaler ADC and NetScaler Gateway.
How do I remediate CVE-2023-3519?
No fix for CVE-2023-3519 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Citrix Systems, Inc.) lists Citrix NetScaler ADC versions 13.1 up to but not including 49.13, 13.0 up to but not including 91.13, 13.1-FIPS up to but not including 37.159, 12.1-FIPS up to but not including 55.297 and 1 more range; Citrix NetScaler Gateway versions 13.1 up to but not including 49.13 and 13.0 up to but not including 91.13 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-3519

Explore →

Is Your Infrastructure Affected by CVE-2023-3519?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.