CVE-2020-13671

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-01-18), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

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

Also known asEUVD-2021-2168 (ENISA EUVD) · GHSA-68jc-v27h-vhmw (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 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
CISA-KEV: ExploitedEPSS PROB: 31%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Drupal core does not properly sanitize certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extension and served as the wrong MIME type or executed as PHP for certain hosting configurations. This issue affects: Drupal Drupal Core 9.0 versions prior to 9.0.8, 8.9 versions prior to 8.9.9, 8.8 versions prior to 8.8.11, and 7 versions prior to 7.74.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
80
EG Risk 80/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.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: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
31%
EPSS %ILE
98th
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.8 HIGH.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
31% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV 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.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines 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.

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 updates per vendor instructions.”

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://nvd.nist.gov/vuln/detail/CVE-2020-13671

Published

November 20, 2020

Last Modified

November 3, 2025

Advisory Details (4)

Auto-updated Nov 9, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. 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-2020-13671
Web page

Drupal core - Critical - Remote code execution - SA-CORE-2020-012 | Drupal.org

https://www.drupal.org/sa-core-2020-012
Web page

[SECURITY] Fedora 33 Update: drupal8-8.9.11-1.fc33 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KWM4CTMEGAC4I2CHYNJVSROY4CVXVEUT/
Web page

[SECURITY] Fedora 32 Update: drupal8-8.9.11-1.fc32 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5KSFM672XW3X6BR7TVKRD63SLZGKK437/

Vendor Advisories for CVE-2020-13671(1)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntudrupal7 (7.26-1ubuntu0.1+esm2) @ trusty2026-11-02ubuntu
ubuntudrupal7 (7.44-1ubuntu1~16.04.0+esm2) @ xenial2026-11-02ubuntu
composerdrupal/core @ 7.74 (fixes >= 7.0.0, < 7.74)—ghsa
composerdrupal/core @ 9.0.8 (fixes >= 9.0.0, < 9.0.8)—ghsa
composerdrupal/core @ 8.8.11 (fixes >= 8.0.0, < 8.8.11)—ghsa
composerdrupal/core @ 8.9.9 (fixes >= 8.9.0, < 8.9.9)—ghsa

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

(13 across 12 ecosystems)
Packagist(2)
PackageVulnerable rangeFix by version rangeDependents
drupal/core8.0.0 ... 8.8.9 (138 versions)
  • 8.0.0 up to 8.8.11: fixed in 8.8.11
  • 8.9.0 up to 8.9.9: fixed in 8.9.9
  • 9.0.0 up to 9.0.8: fixed in 9.0.8
  • 7.0.0 up to 7.74: fixed in 7.74
—
drupal/drupal9.0.0 ... 9.0.7 (8 versions)
  • 7.0.0 up to 7.74: fixed in 7.74
  • 8.0.0 up to 8.8.11: fixed in 8.8.11
  • 8.9.0 up to 8.9.9: fixed in 8.9.9
  • 9.0.0 up to 9.0.8: fixed in 9.0.8
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
drupal7—
  • every version up to 7.74-r0: fixed in 7.74-r0
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
drupal77.52-2 ... 7.52-2+deb9u9 (12 versions)
  • every version up to 7.52-2+deb9u12: fixed in 7.52-2+deb9u12
—

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 12× in last 7d / 50× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 938 rows 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 838 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:38 UTCEPSS rescoreEPSS 31% · 98th percentile
  2. 2026-11-12 19:30 UTCEchelonGraph re-scored
  3. 2026-11-12 19:30 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-12 16:29 UTCEPSS rescoreEPSS 31% · 98th percentile
  5. 2026-11-11 19:06 UTCEchelonGraph re-scored
  6. 2026-11-11 19:06 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-11-11 16:30 UTCEPSS rescoreEPSS 31% · 98th percentile
  8. 2026-11-10 18:39 UTCEchelonGraph re-scored
  9. 2026-11-10 18:39 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-11-10 16:34 UTCEPSS rescoreEPSS 36% · 98th percentile
  11. 2026-11-09 18:15 UTCEchelonGraph re-scored
  12. 2026-11-09 18:15 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-11-09 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  14. 2026-11-08 17:51 UTCEchelonGraph re-scored
  15. 2026-11-08 17:51 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-11-07 17:27 UTCEchelonGraph re-scored
  17. 2026-11-07 17:27 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-11-07 16:32 UTCEPSS rescoreEPSS 36% · 98th percentile
  19. 2026-11-06 17:03 UTCEchelonGraph re-scored
  20. 2026-11-06 17:03 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-11-06 16:29 UTCEPSS rescoreEPSS 36% · 98th percentile
  22. 2026-11-05 16:39 UTCEchelonGraph re-scored
  23. 2026-11-05 16:39 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-11-05 16:29 UTCEPSS rescoreEPSS 36% · 98th percentile
  25. 2026-11-04 16:29 UTCEPSS rescoreEPSS 36% · 98th percentile
Show 75 more
  1. 2026-11-04 16:14 UTCEchelonGraph re-scored
  2. 2026-11-04 16:14 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-03 16:36 UTCEPSS rescoreEPSS 36% · 98th percentile
  4. 2026-11-03 15:48 UTCEchelonGraph re-scored
  5. 2026-11-03 15:48 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-11-03 08:55 UTCOSV refresh
  7. 2026-11-02 15:23 UTCEchelonGraph re-scored
  8. 2026-11-02 15:23 UTCVendor advisory
  9. 2026-11-02 15:23 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-11-01 14:59 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-11-01 08:38 UTCGHSA enrichmentGHSA-68jc-v27h-vhmw · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-11-01 08:38 UTCEchelonGraph re-scored
  13. 2026-10-31 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  14. 2026-10-31 14:35 UTCEchelonGraph re-scored
  15. 2026-10-31 14:35 UTCVendor advisory
  16. 2026-10-30 16:29 UTCEPSS rescoreEPSS 36% · 98th percentile
  17. 2026-10-30 14:10 UTCEchelonGraph re-scored
  18. 2026-10-30 14:10 UTCVendor advisory
  19. 2026-10-29 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  20. 2026-10-29 13:46 UTCEchelonGraph re-scored
  21. 2026-10-29 13:46 UTCVendor advisory
  22. 2026-10-28 16:27 UTCEPSS rescoreEPSS 36% · 98th percentile
  23. 2026-10-28 13:21 UTCEchelonGraph re-scored
  24. 2026-10-28 13:21 UTCVendor advisory
  25. 2026-10-27 16:27 UTCEPSS rescoreEPSS 36% · 98th percentile
  26. 2026-10-27 12:56 UTCEchelonGraph re-scored
  27. 2026-10-25 18:51 UTCEchelonGraph re-scored
  28. 2026-10-25 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  29. 2026-10-25 12:04 UTCEchelonGraph re-scored
  30. 2026-10-24 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  31. 2026-10-24 11:37 UTCEchelonGraph re-scored
  32. 2026-10-24 11:37 UTCVendor advisory
  33. 2026-10-23 16:27 UTCEPSS rescoreEPSS 36% · 98th percentile
  34. 2026-10-23 11:12 UTCEchelonGraph re-scored
  35. 2026-10-23 11:12 UTCVendor advisory
  36. 2026-10-22 10:48 UTCEchelonGraph re-scored
  37. 2026-10-21 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  38. 2026-10-21 10:22 UTCEchelonGraph re-scored
  39. 2026-10-21 10:22 UTCVendor advisory
  40. 2026-10-20 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  41. 2026-10-20 09:58 UTCEchelonGraph re-scored
  42. 2026-10-20 09:58 UTCVendor advisory
  43. 2026-10-19 16:27 UTCEPSS rescoreEPSS 36% · 98th percentile
  44. 2026-10-19 09:31 UTCEchelonGraph re-scored
  45. 2026-10-18 09:06 UTCEchelonGraph re-scored
  46. 2026-10-18 09:06 UTCVendor advisory
  47. 2026-10-17 16:28 UTCEPSS rescoreEPSS 36% · 98th percentile
  48. 2026-10-17 08:40 UTCEchelonGraph re-scored
  49. 2026-10-16 16:32 UTCEPSS rescoreEPSS 35% · 98th percentile
  50. 2026-10-16 08:14 UTCEchelonGraph re-scored
  51. 2026-10-16 08:14 UTCVendor advisory
  52. 2026-10-15 16:27 UTCEPSS rescoreEPSS 35% · 98th percentile
  53. 2026-10-15 07:48 UTCEchelonGraph re-scored
  54. 2026-10-15 07:48 UTCVendor advisory
  55. 2026-10-14 16:28 UTCEPSS rescoreEPSS 35% · 98th percentile
  56. 2026-10-14 07:23 UTCEchelonGraph re-scored
  57. 2026-10-14 07:23 UTCVendor advisory
  58. 2026-10-13 16:28 UTCEPSS rescoreEPSS 35% · 98th percentile
  59. 2026-10-13 06:58 UTCVendor advisory
  60. 2026-10-12 19:46 UTCEchelonGraph re-scored
  61. 2026-10-12 06:33 UTCVendor advisory
  62. 2026-10-12 02:19 UTCVendor advisory
  63. 2026-10-11 22:08 UTCEchelonGraph re-scored
  64. 2026-10-11 22:08 UTCVendor advisory
  65. 2026-10-11 17:55 UTCEchelonGraph re-scored
  66. 2026-10-11 13:44 UTCEchelonGraph re-scored
  67. 2026-10-11 13:42 UTCEPSS rescoreEPSS 35% · 98th percentile
  68. 2026-10-11 09:33 UTCVendor advisory
  69. 2026-10-11 05:22 UTCVendor advisory
  70. 2026-10-10 20:58 UTCEchelonGraph re-scored
  71. 2026-10-10 19:56 UTCEPSS rescoreEPSS 35% · 98th percentile
  72. 2026-10-10 12:32 UTCVendor advisory
  73. 2026-10-10 08:22 UTCVendor advisory
  74. 2026-10-10 04:12 UTCVendor advisory
  75. 2026-10-10 00:02 UTCEchelonGraph re-scored

Frequently asked(6)

What is CVE-2020-13671?
CVE-2020-13671 is a critical-severity vulnerability; its CVE record was published on November 20, 2020. Drupal core does not properly sanitize certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extension and served as the wrong MIME type or executed as PHP for certain hosting configurations. This issue affects: Drupal Drupal Core 9.0 versions prior to…
When was the CVE record for CVE-2020-13671 published?
The CVE record for CVE-2020-13671 was published on November 20, 2020. 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 November 3, 2025; the record at its source may have been updated since.
Is CVE-2020-13671 actively exploited?
Yes. CISA added CVE-2020-13671 to the Known Exploited Vulnerabilities catalog on January 18, 2022, affecting Drupal Drupal core. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2020-13671?
CVE-2020-13671 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2020-13671?
CVE-2020-13671 affects Drupal Drupal core. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2020-13671?
A fix for CVE-2020-13671 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-13671 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2020-13671?

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