CVE-2020-15148

HIGHNVD 8.99.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 79% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 8.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.9
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
CISA-KEV: Not listedEPSS: 79%CVSS: 8.9Exploit: NoneExposed: 0

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

Yii 2 (yiisoft/yii2) before version 2.0.38 is vulnerable to remote code execution if the application calls unserialize() on arbitrary user input. This is fixed in version 2.0.38. A possible workaround without upgrading is available in the linked advisory.

CVSS v3
8.9
EG Score
9.0(high)
EG Risk
77(Track)
EG Risk 77/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
Severity90% × 45%
Exploitation79% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.6%
KEV
Not listed

Published

September 15, 2020

Last Modified

November 21, 2024

References (4)

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
yiisoft/yii22.0.0 ... 2.0.9 (52 versions)2.0.38—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 23× 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.10
  2. 2026-07-22 22:35 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-16 16:59 UTCEPSS rescore
  7. 2026-07-15 16:55 UTCEPSS rescore
  8. 2026-07-13 22:27 UTCEPSS rescore
  9. 2026-07-13 22:27 UTCEPSS rescore
  10. 2026-07-13 03:07 UTCOSV refresh
  11. 2026-07-11 08:25 UTCEPSS rescore
  12. 2026-07-11 08:25 UTCEPSS rescore
  13. 2026-07-08 15:12 UTCEPSS rescore
  14. 2026-07-05 02:27 UTCEPSS rescore
  15. 2026-07-01 15:03 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 12:48 UTCOSV refresh
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 17 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-17 17:50 UTCEPSS rescore
  3. 2026-06-15 17:46 UTCEPSS rescore
  4. 2026-06-14 23:15 UTCEPSS rescore
  5. 2026-06-14 23:15 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-08 14:15 UTCEPSS rescore
  8. 2026-06-08 14:15 UTCEPSS rescore
  9. 2026-06-07 17:16 UTCOSV refresh
  10. 2026-06-06 13:45 UTCEPSS rescore
  11. 2026-06-06 13:45 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-05 22:45 UTCEPSS rescore
  14. 2026-06-05 22:45 UTCEPSS rescore
  15. 2026-06-02 20:11 UTCEPSS rescore
  16. 2026-06-02 20:11 UTCEPSS rescore
  17. 2026-05-23 07:48 UTCEG score recompute

Publicly available exploits

(3 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-15148
    First seen Oct 27, 2020

    cve-2020-15148

    Open source ↗
  • GitHub PoCMaskhe/CVE-2020-15148-bypasses
    First seen Sep 21, 2020

    几条关于CVE-2020-15148（yii2反序列化）的绕过

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

    Yii 2 < 2.0.38 - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-15148?
CVE-2020-15148 is a high vulnerability published on September 15, 2020. Yii 2 (yiisoft/yii2) before version 2.0.38 is vulnerable to remote code execution if the application calls unserialize() on arbitrary user input. This is fixed in version 2.0.38. A possible workaround without upgrading is available in the linked advisory.
When was CVE-2020-15148 disclosed?
CVE-2020-15148 was first published in the National Vulnerability Database on September 15, 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-15148 actively exploited?
CVE-2020-15148 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-15148?
CVE-2020-15148 has a CVSS v3 base score of 8.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2020-15148?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-15148, 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-15148

Explore →

Is Your Infrastructure Affected by CVE-2020-15148?

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

Start Free Scan →Browse All CVEs