SupersetApplication · Apache

CVE-2021-32609

MEDIUM · 5.4 CVSS v3.1 Published 2021-10-18
Fix available
A fix is available. Upgrade to after 1.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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.1 does not sanitize titles correctly on the Explore page. This allows an attacker with Explore access to save a chart with a malicious title, injecting html (including scripts) into the page.

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

Cross-site scripting (XSS) vulnerability in Apache Superset versions up to 1.1 where chart titles on the Explore page are not properly sanitized, allowing injection of HTML and JavaScript through maliciously crafted chart titles by users with Explore access.

MitigationUpgrade Apache Superset to version 1.2 or later which contains the fix. If unable to upgrade, audit existing charts for malicious titles and implement input validation/sanitization on the Explore page before saving chart titles.

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.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Determine Apache Superset version
    Run 'pip show apache-superset' or check the version in your package manager. If using a Docker deployment, check the image tag or run 'superset version' if available.
    Affected if The installed version is 1.1 or lower (any version up to and including 1.1).
  2. Verify Explore functionality is accessible
    Log in as a user with Explore access and navigate to the Explore page (typically /superset/explore/). Confirm the page loads and allows chart creation/editing.
    Affected if The Explore page is accessible and users can create or edit charts.
  3. Inspect existing chart titles for malicious content
    Query the charts table in the Superset metadata database. Look for chart titles containing HTML tags (<script>, <img>, <iframe>, onerror, javascript:, etc.) or unusual character sequences that may indicate XSS payloads.
    Affected if Any chart title contains unsanitized HTML or JavaScript code that could execute in a browser.
  4. Check database for stored XSS patterns
    Run a SQL query on the dashboards or slices table (depending on your Superset version) filtering for title fields with patterns like '<script', 'onerror=', 'javascript:', or other HTML/script tags.
    Affected if Chart or dashboard titles in the database contain raw HTML or JavaScript tags.

You are affected if you run Apache Superset version 1.1 or lower AND the Explore feature is accessible to users, regardless of whether malicious chart titles currently exist in your database.

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.1
Interim mitigation

Upgrade Apache Superset to version 1.2 or later which contains the fix. If unable to upgrade, audit existing charts for malicious titles and implement input validation/sanitization on the Explore page before saving chart titles.

Recommended fix Moderate confidence

1.2 or later

  1. Upgrade Apache Superset to version 1.2 or later to obtain the fix for the XSS vulnerability in chart titles
Caveat Standard upgrade considerations apply - review release notes for any configuration or migration changes between 1.1 and 1.2

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

Fix this in Superset Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-32609 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