CVE-2025-52447
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in Salesforce Tableau Server on Windows, Linux (set-initial-sql tabdoc command modules) allows Interface Manipulation (data access to the production database cluster). This issue affects Tableau Server: before 2025.1.3, before 2024.2.12, before 2023.3.19.
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 confidenceAuthorization bypass vulnerability in Tableau Server's set-initial-sql tabdoc command modules allows attackers to manipulate user-controlled keys to bypass authorization checks, potentially gaining unauthorized data access to the production database cluster via interface manipulation.
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< 2023.3.19>= 2024.2, < 2024.2.12>= 2025.1, < 2025.1.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Tableau Server versionRun 'tsm version' or look at the Tableau Server About page in the UI to identify the exact version number installedAffected if Version is < 2023.3.19, OR >= 2024.2 but < 2024.2.12, OR >= 2025.1 but < 2025.1.3
-
Identify if set-initial-sql tabdoc modules are in useSearch Tableau Server configuration files and published workbooks for any 'set-initial-sql' or 'initial sql' configurations that allow custom SQL at datasource connection timeAffected if set-initial-sql functionality is configured or enabled for any datasource
-
Review datasource connection permissionsCheck Tableau Server repository for published datasources using custom SQL and verify the associated user permissions and data source access controlsAffected if Datasources with custom SQL have overly permissive access grants to untrusted users or groups
-
Audit recent tabdoc command activityReview Tableau Server logs (specifically tabadmin and vizportal logs) for any set-initial-sql command executions or configuration changes from non-admin accountsAffected if Non-administrator users have successfully modified initial SQL configurations or accessed the tabdoc command modules
You are affected if your Tableau Server version falls within the vulnerable ranges AND set-initial-sql datasource connections are in use with user-modifiable configurations.
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 · scoped2023.3.192024.2.122025.1.3
Upgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to remediate the vulnerability.
Tableau Server 2025.1.3 (or 2024.2.12 or 2023.3.19 depending on current version - upgrade to the earliest fixed version >= current major version)
- Identify current Tableau Server version using the Tableau Server Administration console or tabcmd commands
- Determine the appropriate upgrade path based on current version: if < 2023.3.19 upgrade to 2023.3.19; if >= 2024.2 and < 2024.2.12 upgrade to 2024.2.12; if >= 2025.1 and < 2025.1.3 upgrade to 2025.1.3
- Review Tableau Server upgrade documentation for the specific version jump at help.salesforce.com
- Create a full backup of the Tableau Server repository database (pgsql for PostgreSQL) and file store
- Stop all Tableau Server services using TSM (Tableau Services Manager) or the Windows Services console
- Run the Tableau Server installer for the target fixed version
- Run post-upgrade tasks including database migration using TSM commands
- Verify all services started successfully and test the set-initial-sql functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52447 — 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-2025-52447 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