dbcve.org
SupersetApplication · Apache

CVE-2024-53949

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 4.1.0 or later.
See remediation →
71/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
Improper Authorization vulnerability in Apache Superset when FAB_ADD_SECURITY_API is enabled (disabled by default). Allows for lower privilege users to use this API.  issue affects Apache Superset: from 2.0.0 before 4.1.0. Users are recommended to upgrade to version 4.1.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 · moderate confidence

Improper authorization vulnerability in Apache Superset where the FAB_ADD_SECURITY_API (disabled by default) does not properly enforce access controls, allowing lower-privilege users to access this administrative API functionality intended only for higher-privileged users.

MitigationUpgrade Apache Superset to version 4.1.0 or later. If immediate upgrade is not feasible, ensure FAB_ADD_SECURITY_API remains disabled and implement compensating controls.

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:>= 2.0.0, < 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Check installed Apache Superset version
    Run `superset version` or inspect the package version (e.g., `pip show apache-superset` or check the version file in the installation directory)
    Affected if Version is 2.0.0 or higher but lower than 4.1.0
  2. Verify FAB_ADD_SECURITY_API configuration setting
    Inspect the Superset configuration file (superset_config.py) or environment variables for the FAB_ADD_SECURITY_API setting. Check if it is explicitly set to True or enabled.
    Affected if FAB_ADD_SECURITY_API is set to True or enabled (the vulnerability only applies when this feature is turned on)
  3. Confirm presence of lower-privilege users
    Query the user database or access the FAB security admin interface to list users and their assigned roles. Identify users with roles below admin-level privileges.
    Affected if There are non-admin users with access to the system while FAB_ADD_SECURITY_API is enabled

You are affected if your Apache Superset version is between 2.0.0 and 4.1.0 (exclusive) AND FAB_ADD_SECURITY_API is enabled, allowing any lower-privilege user to potentially access administrative API endpoints.

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 Apache Superset to version 4.1.0 or later. If immediate upgrade is not feasible, ensure FAB_ADD_SECURITY_API remains disabled and implement compensating controls.

Recommended fix High confidence

4.1.0

  1. Review the Apache Superset 4.1.0 release notes for any breaking changes and new features
  2. Back up your current Superset database and configuration
  3. Stop the Superset service
  4. Upgrade Superset to version 4.1.0 using your package manager (e.g., pip install apache-superset==4.1.0)
  5. Run any required database migrations (typically: superset db upgrade)
  6. Restart the Superset service
  7. Verify the upgrade was successful and that the FAB_ADD_SECURITY_API authorization issue is resolved
Caveat Review 4.1.0 release notes for potential breaking changes; major version upgrades may include schema or API changes

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

Fix this in Superset Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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