CVE-2020-24881

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 73.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS PROB: 73%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

SSRF exists in osTicket before 1.14.3, where an attacker can add malicious file to server or perform port scanning.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
78(Track*)
EG Risk 78/100SSVC: Track*

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
Severity98% × 45%
Exploitation73% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
73%
EPSS %ILE
99%
KEV
Not listed

Published

November 2, 2020

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Sep 12, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit d98c2d096aeb (osTicket/osTicket)

Patch available: osTicket/osTicket v1.15.4 (contains commit d98c2d096aeb)

https://github.com/osTicket/osTicket/commit/d98c2d096aeb8876c6ab2f88317cd371d781f14d
generic

Locked Out | Packet Storm

http://packetstormsecurity.com/files/160995/osTicket-1.14.2-Server-Side-Request-Forgery.html
generic

Medium

https://blackbatsec.medium.com/cve-2020-24881-server-side-request-forgery-in-osticket-eea175e147f0

Vendor Advisories for CVE-2020-24881(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 19× 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-09-18 19:23 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-17 19:22 UTCEPSS rescore
  4. 2026-09-16 14:04 UTCEPSS rescore
  5. 2026-09-13 16:42 UTCEPSS rescore
  6. 2026-09-12 14:56 UTCEPSS rescore
  7. 2026-09-11 14:48 UTCEPSS rescore
  8. 2026-09-10 09:29 UTCEPSS rescore
  9. 2026-09-07 15:57 UTCEPSS rescore
  10. 2026-09-06 13:44 UTCEPSS rescore
  11. 2026-09-05 15:24 UTCEPSS rescore
  12. 2026-09-04 13:57 UTCEPSS rescore
  13. 2026-09-04 05:03 UTCEPSS rescore
  14. 2026-09-01 03:05 UTCOSV refresh
  15. 2026-08-30 19:14 UTCEPSS rescore
  16. 2026-08-30 01:18 UTCEPSS rescore
  17. 2026-08-26 14:42 UTCEPSS rescore
  18. 2026-08-25 13:45 UTCEPSS rescore
  19. 2026-08-21 23:45 UTCEPSS rescore
  20. 2026-08-19 17:00 UTCEPSS rescore
  21. 2026-08-18 13:44 UTCEPSS rescore
  22. 2026-08-17 13:43 UTCEPSS rescore
  23. 2026-08-16 02:11 UTCEPSS rescore
  24. 2026-08-15 02:30 UTCOSV refresh
  25. 2026-08-15 01:26 UTCEPSS rescore
Show 61 more
  1. 2026-08-13 21:57 UTCEPSS rescore
  2. 2026-08-12 13:47 UTCEPSS rescore
  3. 2026-08-08 16:33 UTCEPSS rescore
  4. 2026-08-06 13:43 UTCEPSS rescore
  5. 2026-08-03 10:32 UTCEPSS rescore
  6. 2026-07-30 16:25 UTCEPSS rescore
  7. 2026-07-30 14:44 UTCOSV refresh
  8. 2026-07-28 15:32 UTCEPSS rescore
  9. 2026-07-25 14:15 UTCEPSS rescore
  10. 2026-07-25 14:14 UTCEPSS rescore
  11. 2026-07-24 14:14 UTCEPSS rescore
  12. 2026-07-23 01:51 UTCEG score recompute
  13. 2026-07-22 22:37 UTCEG score recompute
  14. 2026-07-22 14:05 UTCEPSS rescore
  15. 2026-07-21 15:22 UTCEPSS rescore
  16. 2026-07-21 15:22 UTCEPSS rescore
  17. 2026-07-20 17:04 UTCEPSS rescore
  18. 2026-07-20 17:04 UTCEPSS rescore
  19. 2026-07-15 16:55 UTCEPSS rescore
  20. 2026-07-15 01:57 UTCEPSS rescore
  21. 2026-07-13 06:10 UTCEPSS rescore
  22. 2026-07-13 06:10 UTCEPSS rescore
  23. 2026-07-13 00:07 UTCOSV refresh
  24. 2026-07-12 05:44 UTCEPSS rescore
  25. 2026-07-09 19:07 UTCEPSS rescore
  26. 2026-07-05 02:27 UTCEPSS rescore
  27. 2026-07-01 15:03 UTCEPSS rescore
  28. 2026-06-30 23:20 UTCEPSS rescore
  29. 2026-06-30 23:20 UTCEPSS rescore
  30. 2026-06-28 14:05 UTCEPSS rescore
  31. 2026-06-27 03:06 UTCEPSS rescore
  32. 2026-06-25 13:47 UTCEPSS rescore
  33. 2026-06-24 14:03 UTCEPSS rescore
  34. 2026-06-24 14:03 UTCEPSS rescore
  35. 2026-06-24 09:30 UTCOSV refresh
  36. 2026-06-23 21:31 UTCEPSS rescore
  37. 2026-06-23 21:31 UTCEPSS rescore
  38. 2026-06-19 19:23 UTCEPSS rescore
  39. 2026-06-17 17:50 UTCEPSS rescore
  40. 2026-06-15 17:46 UTCEPSS rescore
  41. 2026-06-12 23:10 UTCEPSS rescore
  42. 2026-06-10 22:16 UTCEPSS rescore
  43. 2026-06-10 22:16 UTCEPSS rescore
  44. 2026-06-07 14:00 UTCOSV refresh
  45. 2026-06-06 13:45 UTCEPSS rescore
  46. 2026-06-06 13:45 UTCEPSS rescore
  47. 2026-06-05 22:45 UTCEPSS rescore
  48. 2026-06-05 22:45 UTCEPSS rescore
  49. 2026-06-02 20:11 UTCEPSS rescore
  50. 2026-06-02 20:11 UTCEPSS rescore
  51. 2026-06-01 13:50 UTCEPSS rescore
  52. 2026-06-01 13:50 UTCEPSS rescore
  53. 2026-05-31 22:29 UTCEPSS rescore
  54. 2026-05-31 22:29 UTCEPSS rescore
  55. 2026-05-27 13:39 UTCEPSS rescore
  56. 2026-05-26 13:42 UTCEPSS rescore
  57. 2026-05-26 13:42 UTCEPSS rescore
  58. 2026-05-26 07:17 UTCEPSS rescore
  59. 2026-05-26 07:17 UTCEPSS rescore
  60. 2026-05-23 05:46 UTCEG score recompute
  61. 2026-05-23 05:46 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-49441
    First seen Jan 19, 2021

    osTicket 1.14.2 - SSRF

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-24881.yaml
    First seen Jan 1, 2020

    OsTicket < 1.14.3 - Server Side Request Forgery

    Open source ↗

Frequently asked(5)

What is CVE-2020-24881?
CVE-2020-24881 is a critical vulnerability published on November 2, 2020. SSRF exists in osTicket before 1.14.3, where an attacker can add malicious file to server or perform port scanning.
When was CVE-2020-24881 disclosed?
CVE-2020-24881 was first published in the National Vulnerability Database on November 2, 2020, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-24881 actively exploited?
CVE-2020-24881 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73% probability of exploitation in the next 30 days, which ranks it in the top 0.6% of all scored CVEs.
What is the CVSS score of CVE-2020-24881?
CVE-2020-24881 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-24881?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-24881, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-24881

Explore →

Is Your Infrastructure Affected by CVE-2020-24881?

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

Start Free Scan →Browse All CVEs