+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2020-13671 Drupal core Un-restricted Upload of File

Improper sanitization in the extension file names is present in Drupal core.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 18 Jan 2022.
  • Rated High severity (CVSS 8.8, scored by CISA).
  • It has been in the catalogue for 1,753 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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.

Affected Versions

ProductVersions
Drupal Drupal Core9.0 versions prior to 9.0.8
8.9 versions prior to 8.9.9
8.8 versions prior to 8.8.11
7 versions prior to 7.74

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Drupal core. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated high, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 18 Jul 2022 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Drupal Flaws

Get alerts for DrupalWe email you when a new Drupal vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2026-9082Drupal Core SQL Injection VulnerabilityAdded 22 May 2026CVE-2018-7602 · RansomwareDrupal Core Remote Code Execution VulnerabilityAdded 13 Apr 2022CVE-2019-6340Drupal Core Remote Code Execution VulnerabilityAdded 25 Mar 2022CVE-2018-7600 · RansomwareDrupal Core Remote Code Execution VulnerabilityAdded 3 Nov 2021

All 5 exploited Drupal vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2020-13671 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2020-13671
  3. CVE record: CVE-2020-13671
  4. FIRST EPSS
  5. drupal.org/sa-core-2020-012
  6. lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KWM4CTMEGAC
  7. lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5KSFM672XW3