SupersetApplication · Apache
CVE-2023-49736
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 where_in JINJA macro allows users to specify a quote, which combined with a carefully crafted statement would allow for SQL injection in Apache Superset.This issue affects Apache Superset: before 2.1.2, from 3.0.0 before 3.0.2. Users are recommended to upgrade to version 3.0.2, 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 confidenceA SQL injection vulnerability exists in Apache Superset's where_in JINJA macro, which allows users to specify quotes that can be combined with crafted statements to inject arbitrary SQL code. This affects versions before 2.1.2 and from 3.0.0 before 3.0.2.
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
< 2.1.2>= 3.0.0, < 3.0.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Superset installationRun 'pip show apache-superset' or check the Docker image version with 'docker images | grep superset'. If using a managed service, check with your cloud provider's tooling.Affected if The installed version is < 2.1.2 or >= 3.0.0 but < 3.0.2
-
Verify database connection permissionsCheck if the Superset service account has permission to create or modify databases. The vulnerability exploits the where_in JINJA macro which is used in SQL queries. Check SQL Lab saved queries and the metadata database for usage of the 'where_in' macro.Affected if The where_in JINJA macro is used in any saved SQL queries or virtual datasets and the Superset version is vulnerable
-
Inspect saved SQL queries and datasetsQuery the metadata database (typically in 'superset.sqllab_query' table) for instances of the string 'where_in' in the SQL text field. Also check 'superset.sqllab_tabs' and any virtual datasets.Affected if SQL queries containing where_in macro exist in the environment and the Superset version is vulnerable
You are affected if your Apache Superset version is in the range < 2.1.2 or >= 3.0.0 and < 3.0.2, AND you have SQL queries using the where_in JINJA macro, OR users can submit custom SQL through SQL Lab.
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 · scoped2.1.23.0.2
Upgrade to Apache Superset version 3.0.2 or later (or version 2.1.2 for the 2.x branch) to resolve this SQL injection vulnerability.
3.0.2 (or 2.1.2 for versions < 2.1.2)
- Identify current Apache Superset version using package manager or UI
- If version is < 2.1.2, upgrade to version 2.1.2 or later
- If version is 3.0.0 or 3.0.1, upgrade to version 3.0.2 or later
- Restart Superset services after upgrade
- Verify the upgrade was successful and test that the where_in JINJA macro functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49736 — 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-49736 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