dbcve.org
SupersetApplication · Apache

CVE-2022-43720

MEDIUM · 5.4 CVSS v3.1 Published 2023-01-16
Fix available
A fix is available. Upgrade to after 1.5.2 or later.
See remediation →
60/100
Remediation priority · Elevated
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
An authenticated attacker with write CSS template permissions can create a record with specific HTML tags that will not get properly escaped by the toast message displayed when a user deletes that specific CSS template record. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.

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

Authenticated users with write CSS template permissions can inject malicious HTML/JavaScript into CSS template records. When another user deletes that template, the toast notification displays the unsanitized template name, leading to reflected XSS execution in the victim's browser.

MitigationUpgrade to a patched version of Apache Superset (post-2.0.0) or implement output encoding/HTML escaping for all user-supplied content displayed in toast notifications, particularly during CSS template deletion operations.

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.5.2= 2.0.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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Identify Apache Superset installation and version
    Locate the Superset installation and determine the installed version by checking package metadata, container labels, or the /health endpoint if available. Compare the version number against the affected ranges: versions <= 1.5.2 or exactly version 2.0.0
    Affected if The installed Superset version is 1.5.2 or lower, or exactly 2.0.0
  2. Confirm CSS Templates feature is enabled
    Check the Superset configuration for the FEATURE_FLAGS or any setting that enables the CSS Templates functionality. This may be found in superset_config.py, environment variables, or the database configuration table
    Affected if The CSS Templates feature flag is enabled in the Superset configuration
  3. Verify user permissions for CSS template write access
    Review role-based access control (RBAC) settings to determine which users or roles have write or editor permissions on CSS templates. Check the permission model for 'css_template' related actions in the Superset security configuration
    Affected if Users other than administrators have write, edit, or delete permissions on CSS templates
  4. Check for existing CSS template records with unsanitized names
    Query the css_templates database table (or equivalent) to inspect template names. Look for template names containing HTML tags (<script>, <img onerror=, iframe, etc.) or JavaScript event handlers
    Affected if CSS template records exist with names containing potentially malicious HTML or JavaScript code that could execute in a toast notification

A user is affected if running Superset version <= 1.5.2 or exactly 2.0.0, the CSS Templates feature is enabled, and users with write permissions to CSS templates exist in the environment.

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

Upgrade to a patched version of Apache Superset (post-2.0.0) or implement output encoding/HTML escaping for all user-supplied content displayed in toast notifications, particularly during CSS template deletion operations.

Recommended fix Moderate confidence

2.0.1 or later

  1. 1. Backup your Superset database and configuration files before upgrading.
  2. 2. Stop the Superset application services.
  3. 3. Upgrade Superset to version 2.0.1 or later using your package manager (e.g., pip install apache-superset==2.0.1 or Helm upgrade for Kubernetes deployments).
  4. 4. Verify the upgrade by checking the installed version: pip show apache-superset
  5. 5. Start the Superset application services.
  6. 6. Test that deleting a CSS template no longer executes embedded HTML/JavaScript in toast notifications.
Caveat Review release notes for 2.0.1 for any breaking changes; minor version upgrades typically have minimal breaking changes

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

Fix this in Superset Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43720 — 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-2022-43720 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