CVE-2019-13345

HIGHNVD 6.18.4▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.4 because EPSS predicts 74% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 6.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.4EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
CISA-KEV: Not listedEPSS PROB: 74%CVSS: 6.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

The cachemgr.cgi web module of Squid through 4.7 has XSS via the user_name or auth parameter.

CVSS v3
6.1
EG Score
8.4HIGHhigh confidence
EG Risk
72
EG Risk 72/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation74% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
74%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 5, 2019

Last Modified

November 21, 2024

References (30)

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntusquidclient (3.5.12-1ubuntu7.7) @ xenial2026-05-27ubuntu
ubuntusquid3 (3.1.19-1ubuntu3.12.04.9) @ precise2026-05-27ubuntu
redhatsquid-7:3.5.20-15.el72020-03-31redhat
redhatsquid:4-8010020190823133019.cdc1202b2019-11-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(25 across 25 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 3.5.27-r1: fixed in 3.5.27-r1
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 3.5.27-r3: fixed in 3.5.27-r3
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-r0: fixed in 4.8-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
squid4.6-1
  • every version up to 4.6-1+deb10u1: fixed in 4.6-1+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-1: fixed in 4.8-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-1: fixed in 4.8-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-1: fixed in 4.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.8-1: fixed in 4.8-1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
squid33.4.8-6 ... 3.4.8-6+deb8u6 (8 versions)
  • every version up to 3.4.8-6+deb8u7: fixed in 3.4.8-6+deb8u7
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
squid33.5.23-5, 3.5.23-5+deb9u1
  • every version up to 3.5.23-5+deb9u2: fixed in 3.5.23-5+deb9u2
—

Weakness Classification(1)

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

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 2× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-09-30 10:10 UTCEG score recompute
  3. 2026-09-28 01:19 UTCOSV refresh
  4. 2026-09-26 15:53 UTCEPSS rescore
  5. 2026-09-24 13:59 UTCEPSS rescore
  6. 2026-09-21 20:27 UTCEPSS rescore
  7. 2026-09-20 20:10 UTCEPSS rescore
  8. 2026-09-18 19:22 UTCEPSS rescore
  9. 2026-09-17 19:22 UTCEPSS rescore
  10. 2026-09-16 14:04 UTCEPSS rescore
  11. 2026-09-15 03:05 UTCEPSS rescore
  12. 2026-09-13 16:42 UTCEPSS rescore
  13. 2026-09-12 14:56 UTCEPSS rescore
  14. 2026-09-08 09:16 UTCOSV refresh
  15. 2026-09-06 13:44 UTCEPSS rescore
  16. 2026-09-05 15:24 UTCEPSS rescore
  17. 2026-09-02 14:07 UTCEPSS rescore
  18. 2026-08-30 19:13 UTCEPSS rescore
  19. 2026-08-30 01:18 UTCEPSS rescore
  20. 2026-08-28 21:36 UTCEPSS rescore
  21. 2026-08-26 14:42 UTCEPSS rescore
  22. 2026-08-21 23:45 UTCEPSS rescore
  23. 2026-08-21 19:14 UTCOSV refresh
  24. 2026-08-19 17:00 UTCEPSS rescore
  25. 2026-08-18 13:44 UTCEPSS rescore
Show 74 more
  1. 2026-08-16 02:10 UTCEPSS rescore
  2. 2026-08-13 21:56 UTCEPSS rescore
  3. 2026-08-12 13:47 UTCEPSS rescore
  4. 2026-08-06 03:21 UTCOSV refresh
  5. 2026-08-05 19:13 UTCEPSS rescore
  6. 2026-07-30 16:24 UTCEPSS rescore
  7. 2026-07-30 01:27 UTCEPSS rescore
  8. 2026-07-26 14:51 UTCEPSS rescore
  9. 2026-07-24 14:14 UTCEPSS rescore
  10. 2026-07-24 14:14 UTCEPSS rescore
  11. 2026-07-23 01:39 UTCEG score recompute▲ 2.30
  12. 2026-07-22 22:19 UTCEG score recompute
  13. 2026-07-22 14:05 UTCEPSS rescore
  14. 2026-07-21 15:22 UTCEPSS rescore
  15. 2026-07-21 15:22 UTCEPSS rescore
  16. 2026-07-20 17:04 UTCEPSS rescore
  17. 2026-07-20 13:32 UTCOSV refresh
  18. 2026-07-16 16:59 UTCEPSS rescore
  19. 2026-07-16 16:59 UTCEPSS rescore
  20. 2026-07-15 16:55 UTCEPSS rescore
  21. 2026-07-12 05:43 UTCEPSS rescore
  22. 2026-07-09 19:06 UTCEPSS rescore
  23. 2026-07-08 15:11 UTCEPSS rescore
  24. 2026-07-05 02:27 UTCEPSS rescore
  25. 2026-07-03 08:26 UTCOSV refresh
  26. 2026-07-02 16:56 UTCEPSS rescore
  27. 2026-07-01 15:03 UTCEPSS rescore
  28. 2026-07-01 15:03 UTCEPSS rescore
  29. 2026-06-30 23:20 UTCEPSS rescore
  30. 2026-06-30 23:20 UTCEPSS rescore
  31. 2026-06-28 14:04 UTCEPSS rescore
  32. 2026-06-28 04:54 UTCEPSS rescore
  33. 2026-06-28 04:53 UTCEPSS rescore
  34. 2026-06-25 13:47 UTCEPSS rescore
  35. 2026-06-25 13:47 UTCEPSS rescore
  36. 2026-06-24 14:03 UTCEPSS rescore
  37. 2026-06-24 14:02 UTCEPSS rescore
  38. 2026-06-23 21:30 UTCEPSS rescore
  39. 2026-06-23 21:30 UTCEPSS rescore
  40. 2026-06-17 17:50 UTCEPSS rescore
  41. 2026-06-16 17:50 UTCEPSS rescore
  42. 2026-06-15 17:45 UTCEPSS rescore
  43. 2026-06-14 23:15 UTCEPSS rescore
  44. 2026-06-14 23:15 UTCEPSS rescore
  45. 2026-06-14 23:13 UTCOSV refresh
  46. 2026-06-13 22:58 UTCEPSS rescore
  47. 2026-06-12 23:09 UTCEPSS rescore
  48. 2026-06-11 13:58 UTCEPSS rescore
  49. 2026-06-11 13:58 UTCEPSS rescore
  50. 2026-06-10 22:16 UTCEPSS rescore
  51. 2026-06-10 13:19 UTCEPSS rescore
  52. 2026-06-08 14:15 UTCEPSS rescore
  53. 2026-06-08 14:14 UTCEPSS rescore
  54. 2026-06-07 15:23 UTCEPSS rescore
  55. 2026-06-07 15:22 UTCEPSS rescore
  56. 2026-06-05 22:45 UTCEPSS rescore
  57. 2026-06-05 22:45 UTCEPSS rescore
  58. 2026-06-05 06:08 UTCEPSS rescore
  59. 2026-06-05 06:08 UTCEPSS rescore
  60. 2026-06-04 13:10 UTCEPSS rescore
  61. 2026-06-04 13:10 UTCEPSS rescore
  62. 2026-06-02 20:11 UTCEPSS rescore
  63. 2026-05-31 22:29 UTCEPSS rescore
  64. 2026-05-31 22:29 UTCEPSS rescore
  65. 2026-05-31 00:14 UTCEPSS rescore
  66. 2026-05-31 00:14 UTCEPSS rescore
  67. 2026-05-29 13:42 UTCEPSS rescore
  68. 2026-05-28 13:43 UTCEPSS rescore
  69. 2026-05-27 17:38 UTCEG score recompute
  70. 2026-05-27 17:38 UTCVendor advisory
  71. 2026-05-27 17:38 UTCGHSA enrichment
  72. 2026-05-26 07:17 UTCEPSS rescore
  73. 2026-05-26 07:17 UTCEPSS rescore
  74. 2026-05-26 03:46 UTCOSV refresh

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-13345?
CVE-2019-13345 is a high vulnerability published on July 5, 2019. The cachemgr.cgi web module of Squid through 4.7 has XSS via the user_name or auth parameter.
When was CVE-2019-13345 disclosed?
CVE-2019-13345 was first published on July 5, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-13345 actively exploited?
CVE-2019-13345 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 74% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-13345?
CVE-2019-13345 has a CVSS v3 base score of 6.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.4 (HIGH).
How do I remediate CVE-2019-13345?
A fix for CVE-2019-13345 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-13345

Explore →

Is Your Infrastructure Affected by CVE-2019-13345?

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

Book a Demo →Browse All CVEs