dbcve.org
SupersetApplication · Apache

CVE-2023-43701

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-27
Fix available
A fix is available. Upgrade to 2.1.2 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
Improper payload validation and an improper REST API response type, made it possible for an authenticated malicious actor to store malicious code into Chart's metadata, this code could get executed if a user specifically accesses a specific deprecated API endpoint. This issue affects Apache Superset versions prior to 2.1.2.  Users are recommended to upgrade to version 2.1.2, which fixes this 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

Apache Superset versions before 2.1.2 have improper payload validation and improper REST API response type handling, allowing an authenticated attacker to store malicious code in Chart metadata. This stored code executes when users access a specific deprecated API endpoint, representing a stored Cross-Site Scripting (XSS) vulnerability.

MitigationUpgrade Apache Superset to version 2.1.2 or later to resolve the improper payload validation and improper REST API response type issues.

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.1.2

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 Apache Superset version
    Check the installed package version using your package manager (e.g., pip show apache-superset, docker image inspect, or check the superset config/API endpoint /api/v1/version)
    Affected if The installed version is any version before 2.1.2 (e.g., 2.1.1, 2.1.0, 2.0.x, 1.x series)
  2. Confirm Chart metadata feature is accessible
    Verify if the Chart metadata editing feature is available in the Superset UI or via API (POST to /api/v1/chart/ with metadata payload)
    Affected if The authenticated user has permissions to create or edit Charts and can modify chart metadata fields
  3. Verify deprecated API endpoint accessibility
    Attempt to access or identify the deprecated API endpoint that executes stored chart metadata code (typically legacy /superset/explore or similar deprecated endpoints)
    Affected if Deprecated API endpoints are accessible to users and the Superset version is below 2.1.2

If Apache Superset version is below 2.1.2 and users have Chart metadata edit permissions with access to deprecated API endpoints, the environment is vulnerable to stored XSS via Chart metadata.

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

Upgrade Apache Superset to version 2.1.2 or later to resolve the improper payload validation and improper REST API response type issues.

Recommended fix High confidence

2.1.2

  1. 1. Review the Apache Superset 2.1.2 release notes and changelog for any breaking changes or migration requirements
  2. 2. Create a backup of your current Superset database and configuration
  3. 3. Stop the Superset application and any related services
  4. 4. Upgrade Apache Superset to version 2.1.2 using your package manager (e.g., pip install apache-superset==2.1.2 or pip install apache-superset --upgrade)
  5. 5. Run database migrations if required: superset db upgrade
  6. 6. Restart the Superset application services
  7. 7. Verify the upgrade was successful by logging in and checking the version number in the UI
  8. 8. Test that the deprecated API endpoint mentioned in the vulnerability is no longer accessible or has been patched
Caveat Review the 2.1.2 release notes for any breaking changes; major version upgrades may include configuration or feature changes that require migration steps

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

Fix this in Superset Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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