SupersetApplication · Apache
CVE-2023-49657
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 · uneditedA stored cross-site scripting (XSS) vulnerability exists in Apache Superset before 3.0.3. An authenticated attacker with create/update permissions on charts or dashboards could store a script or add a specific HTML snippet that would act as a stored XSS. For 2.X versions, users should change their config to include: TALISMAN_CONFIG = { "content_security_policy": { "base-uri": ["'self'"], "default-src": ["'self'"], "img-src": ["'self'", "blob:", "data:"], "worker-src": ["'self'", "blob:"], "connect-src": [ "'self'", " https://api.mapbox.com" https://api.mapbox.com" ;, " https://events.mapbox.com" https://events.mapbox.com" ;, ], "object-src": "'none'", "style-src": [ "'self'", "'unsafe-inline'", ], "script-src": ["'self'", "'strict-dynamic'"], }, "content_security_policy_nonce_in": ["script-src"], "force_https": False, "session_cookie_secure": False, }
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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in Apache Superset versions before 3.0.3. An authenticated user with create or update permissions on charts or dashboards can inject malicious scripts or HTML that persist in the database and execute when other users view those affected resources.
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
< 3.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Apache Superset versionRun the command to display the Superset version (e.g., 'superset version' or check the package.json/version file in the Superset installation directory)Affected if The installed version is lower than 3.0.3 (e.g., 3.0.0, 2.5.x, 2.4.x, or any version < 3.0.3)
-
Confirm authentication is enabledVerify that Superset is configured with an authentication mechanism (e.g., database, OAuth, LDAP) and that user login is required to access the applicationAffected if Authentication is enabled and users can log in to Superset
-
Check for users with create or update permissions on charts or dashboardsReview user roles and permissions in the Superset admin panel or configuration to identify which authenticated users have permissions to create or modify charts and dashboardsAffected if There exist authenticated users with create or update permissions on charts or dashboards
-
Inspect stored charts and dashboards for suspicious contentReview the content of saved charts and dashboards in the database or through the Superset UI, looking for unusual JavaScript, HTML tags, or script elements in titles, descriptions, or data configurationsAffected if Any chart or dashboard contains persisted JavaScript or HTML that was not intentionally created by the current user (indicating potential exploitation)
-
Verify if Content Security Policy (CSP) is configuredCheck the Superset configuration (TALISMAN_CONFIG or similar) for Content Security Policy settings that could mitigate XSS executionAffected if No CSP is configured or the TALISMAN_CONFIG is missing, leaving the application vulnerable to XSS execution in browsers
A user is affected if they are running any Apache Superset version below 3.0.3 with authentication enabled and users having create/update permissions on charts or dashboards, especially if no Content Security Policy is configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.0.3
Apply the provided TALISMAN_CONFIG Content Security Policy settings to restrict script execution, and consider upgrading to Superset 3.0.3 or later which contains the security fix.
3.0.3
- 1. Plan and schedule a maintenance window for the upgrade
- 2. Back up your existing Superset database and configuration files
- 3. Upgrade Apache Superset to version 3.0.3 or later by following the official upgrade documentation
- 4. Verify that the upgrade was successful by logging in and testing core functionality
- 5. As an additional defense-in-depth measure for 2.X versions that cannot immediately upgrade, add the TALISMAN_CONFIG to your superset_config.py with the provided Content Security Policy settings
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
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 locallyCheck whether your project pulls in CVE-2023-49657 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49657 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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