dbcve.org
SupersetApplication · Apache

CVE-2025-55672

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-14
Fix available
A fix is available. Upgrade to 5.0.0 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
A stored Cross-Site Scripting (XSS) vulnerability exists in Apache Superset's chart visualization. An authenticated user with permissions to edit charts can inject a malicious payload into a column's label. The payload is not properly sanitized and gets executed in the victim's browser when they hover over the chart, potentially leading to session hijacking or the execution of arbitrary commands on behalf of the user. This issue affects Apache Superset: before 5.0.0. Users are recommended to upgrade to version 5.0.0, which fixes the issue.

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

Stored XSS vulnerability in Apache Superset's chart visualization allows authenticated users with edit permissions to inject malicious JavaScript into column labels. The unsanitized payload executes in victims' browsers when hovering over affected charts, potentially enabling session hijacking or arbitrary command execution.

MitigationUpgrade Apache Superset to version 5.0.0 or later which includes proper input sanitization for column labels.

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:< 5.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
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. Identify installed Apache Superset version
    Run the command `pip show apache-superset` or check the version from the Superset UI under Settings > Information. Alternatively, query the metadata database: SELECT version FROM ab_user WHERE id=1; or check the SUPERSET_VERSION in the codebase.
    Affected if The installed version is lower than 5.0.0
  2. Locate charts with custom column labels
    Query the metadata database tables related to charts/datasets, typically `slices` or `datasources` tables. Look for configurations where `column_label` or similar fields are defined.
    Affected if Charts exist that use custom column labels rather than default column names
  3. Inspect column label content for unsanitized input
    Examine the stored column label values in the database or UI. In the Superset UI, open chart configuration and check the 'Columns' or 'Metrics' settings where labels are defined.
    Affected if Any column label contains HTML tags, script elements, or JavaScript event handlers (e.g., <script>, onload=, onerror=, javascript:)
  4. Verify user permissions for chart editing
    Check user roles and permissions in Superset under Settings > List of Roles, or query the permission tables. Look for Gamma, Alpha, or custom roles with 'can_edit' or 'can_save' permissions on charts/datasets.
    Affected if Any authenticated user has edit or save permissions on charts (Gamma role or higher)

You are affected if running Apache Superset version < 5.0.0 AND there are charts with user-defined column labels that could contain malicious scripts, AND at least one user with edit permissions exists.

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 5.0.0 or later
Fixed in 5.0.0
Interim mitigation

Upgrade Apache Superset to version 5.0.0 or later which includes proper input sanitization for column labels.

Recommended fix High confidence

5.0.0

  1. 1. Create a complete backup of the current Superset database and configuration files
  2. 2. Stop all Superset services (web server, celery workers, and any running processes)
  3. 3. Upgrade Apache Superset to version 5.0.0 using the appropriate package manager (e.g., pip install apache-superset==5.0.0 or equivalent for your deployment)
  4. 4. Run database migrations: superset db upgrade
  5. 5. Restart all Superset services in the correct order
  6. 6. Verify the upgrade was successful by logging in and checking that charts render correctly
  7. 7. Test that the XSS fix is working by attempting to use special characters in chart column labels
Caveat Review Superset 5.0.0 release notes for any breaking changes or deprecated features before upgrading

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-2025-55672 — 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-2025-55672 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