dbcve.org
SupersetApplication · Apache

CVE-2024-53947

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 4.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Superset. Specifically, certain engine-specific functions are not checked, which allows attackers to bypass Apache Superset's SQL authorization. This issue is a follow-up to CVE-2024-39887 with additional disallowed PostgreSQL functions now included: query_to_xml_and_xmlschema, table_to_xml, table_to_xml_and_xmlschema. This issue affects Apache Superset: <4.1.0. Users are recommended to upgrade to version 4.1.0, which fixes the issue or add these Postgres functions to the config set DISALLOWED_SQL_FUNCTIONS.

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 has a SQL authorization bypass vulnerability where additional PostgreSQL XML-generation functions (query_to_xml_and_xmlschema, table_to_xml, table_to_xml_and_xmlschema) are not included in the disallowed functions list, allowing authenticated attackers to bypass SQL authorization controls and potentially exfiltrate data through these functions.

MitigationUpgrade to Apache Superset version 4.1.0 or add the three PostgreSQL functions to the DISALLOWED_SQL_FUNCTIONS configuration setting.

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:< 4.1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Apache Superset installed version
    Run 'superset version' from the command line, or inspect the version file in the Superset installation directory (typically found in the site-packages or pip show superset output)
    Affected if The installed version is lower than 4.1.0 (e.g., 4.0.x, 3.x, etc.)
  2. Locate the Superset configuration file
    Find the superset_config.py file, commonly located in the path specified by SUPERSET_HOME or in the config directory of your Superset installation
    Affected if You cannot locate a superset_config.py file (default installations may use an unpatched configuration)
  3. Inspect DISALLOWED_SQL_FUNCTIONS setting
    Open superset_config.py and search for the DISALLOWED_SQL_FUNCTIONS configuration entry. It should be defined as a list of disallowed function names
    Affected if Either the DISALLOWED_SQL_FUNCTIONS setting is missing entirely, or it exists but does NOT contain all three functions: 'query_to_xml_and_xmlschema', 'table_to_xml', and 'table_to_xml_and_xmlschema'

You are affected if your Superset version is below 4.1.0 AND your DISALLOWED_SQL_FUNCTIONS configuration does not explicitly include all three PostgreSQL XML-generation functions.

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

Upgrade to Apache Superset version 4.1.0 or add the three PostgreSQL functions to the DISALLOWED_SQL_FUNCTIONS configuration setting.

Recommended fix High confidence

4.1.0

  1. 1. Back up your current Superset installation and database before upgrading
  2. 2. Stop the Superset service
  3. 3. Upgrade Superset to version 4.1.0 using your package manager (e.g., pip install apache-superset==4.1.0 or pip install apache-superset --upgrade)
  4. 4. Run database migrations with 'superset db upgrade'
  5. 5. Restart the Superset service
  6. 6. Verify the upgrade was successful by logging in and checking the version
Caveat Review release notes for any breaking changes between your current version and 4.1.0

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

Fix this in Superset Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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