CVE-2020-13933

HIGHNVD 7.58.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.0 because EPSS predicts 48% probability of exploitation within the next 30 days (top 1.3% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 48%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Apache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass.

CVSS v3
7.5
EG Score
8.0(high)
EG Risk
60(Track)
EG Risk 60/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
Severity80% × 45%
Exploitation48% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.7%
KEV
Not listed

Published

August 17, 2020

Last Modified

November 21, 2024

References (32)

Vendor Advisories for CVE-2020-13933(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibshiro-java (1.3.2-4ubuntu0.2) @ focal2026-05-27ubuntu
redhatshiro-core2021-02-02redhat

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.shiro:shiro-core1.0.0-incubating ... 1.5.3 (20 versions)1.6.0—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • GitHub PoC0xkami/cve-2020-13933
    First seen Sep 23, 2020

    cve-2020-13933 apache shiro权限绕过漏洞

    Open source ↗
  • GitHub PoCEXP-Docs/CVE-2020-13933
    First seen Sep 9, 2020

    CVE-2020-13933 靶场： shiro 认证绕过漏洞

    Open source ↗

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2020-13933?
CVE-2020-13933 is a high vulnerability published on August 17, 2020. Apache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass.
When was CVE-2020-13933 disclosed?
CVE-2020-13933 was first published in the National Vulnerability Database on August 17, 2020, 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-2020-13933 actively exploited?
CVE-2020-13933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-13933?
CVE-2020-13933 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.0.
How do I remediate CVE-2020-13933?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-13933, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-13933

Explore →

Is Your Infrastructure Affected by CVE-2020-13933?

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

Start Free Scan →Browse All CVEs