dbcve.org
SupersetApplication · Apache

CVE-2021-41971

HIGH · 8.8 CVSS v3.1 Published 2021-10-18
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Apache Superset up to and including 1.3.0 when configured with ENABLE_TEMPLATE_PROCESSING on (disabled by default) allowed SQL injection when a malicious authenticated user sends an http request with a custom URL.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Superset versions up to 1.3.0 contain a SQL injection vulnerability in the template processing feature. When ENABLE_TEMPLATE_PROCESSING is enabled (disabled by default), an authenticated user can inject malicious SQL via a custom URL in an HTTP request, potentially allowing unauthorized data access or modification.

MitigationUpgrade Apache Superset to version 1.3.1 or later. Alternatively, if upgrading is not immediately feasible, ensure ENABLE_TEMPLATE_PROCESSING remains disabled (the default) as a compensating control until the upgrade can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SupersetApplication
Affected:<= 1.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Apache Superset version
    Run 'pip show apache-superset' or check the package version in your environment. If using a container, check the image tag or Dockerfile. Compare against affected range <= 1.3.0
    Affected if Superset version is 1.3.0 or earlier
  2. Verify ENABLE_TEMPLATE_PROCESSING setting
    Check Superset configuration file (superset_config.py) or environment variables for ENABLE_TEMPLATE_PROCESSING = True
    Affected if ENABLE_TEMPLATE_PROCESSING is set to True or enabled
  3. Confirm authentication is required for the attack vector
    The vulnerability requires an authenticated user session. Verify that your Superset deployment requires login and that users have access to the template processing feature
    Affected if Unauthenticated or low-privilege users can access the template processing endpoint (default config requires authentication)

You are affected if running Superset version 1.3.0 or earlier AND ENABLE_TEMPLATE_PROCESSING is enabled in your configuration, allowing authenticated users to exploit the SQL injection via template processing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.3.0
Interim mitigation

Upgrade Apache Superset to version 1.3.1 or later. Alternatively, if upgrading is not immediately feasible, ensure ENABLE_TEMPLATE_PROCESSING remains disabled (the default) as a compensating control until the upgrade can be completed.

Recommended fix Moderate confidence

Upgrade to Apache Superset 1.4.0 or later (latest stable release recommended)

  1. 1. Check current Superset version by running 'superset version' or checking the metadata database
  2. 2. Backup the Superset metadata database before upgrading
  3. 3. Ensure ENABLE_TEMPLATE_PROCESSING is disabled (it is disabled by default; verify in superset_config.py: ENBLE_TEMPLATE_PROCESSING = False)
  4. 4. Upgrade Superset by running: pip install apache-superset==1.4.0 or later (pip install apache-superset --upgrade for latest stable)
  5. 5. Run database migrations: superset db upgrade
  6. 6. Restart the Superset web server and any worker processes
  7. 7. Verify the upgrade was successful by checking the version and logging in
Caveat Upgrading Superset may require database migrations; review release notes for 1.4.0+ for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Superset Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-41971 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-41971 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data