dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-52451

HIGH · 8.5 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2023.3.19 / 2024.2.12 or later.
See remediation →
88/100
Remediation priority · High
No privileges

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 Input Validation vulnerability in Salesforce Tableau Server on Windows, Linux (tabdoc api - create-data-source-from-file-upload modules) allows Absolute Path Traversal.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 confidence

Improper input validation in Tableau Server's tabdoc API (create-data-source-from-file-upload modules) allows attackers to perform absolute path traversal, potentially enabling unauthorized file system access by manipulating file paths during upload operations.

MitigationUpgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to patch the path traversal vulnerability in the file upload functionality.

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
Tableau ServerApplication
Affected:< 2023.3.19>= 2024.2, < 2024.2.12>= 2025.1, < 2025.1.3

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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Tableau Server installation
    Locate Tableau Server installation directory or check for running Tableau processes (tabsvc, tabadmin) on the system
    Affected if Tableau Server is not found on the system
  2. Identify Tableau Server version
    Use Tableau Server command-line tools (tsm version or tabcmd version) or check the version displayed in Tableau Server's About section in the web interface
    Affected if Unable to determine the installed version
  3. Compare version against affected ranges
    Check if the installed version falls into any of these ranges: < 2023.3.19; >= 2024.2 and < 2024.2.12; >= 2025.1 and < 2025.1.3
    Affected if Version matches one of the affected ranges indicating vulnerability to path traversal
  4. Assess exposure of file upload API
    Review Tableau Server configuration to determine if the tabdoc API create-data-source-from-file-upload endpoint is accessible (typically exposed via the Vizportal service on ports 8000-8005 or through the Tableau Server web interface)
    Affected if The file upload API endpoint is accessible without additional network restrictions

The environment is affected if Tableau Server is installed with a version in the ranges < 2023.3.19, >= 2024.2 to < 2024.2.12, or >= 2025.1 to < 2025.1.3 AND the tabdoc API file upload functionality is accessible.

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 2023.3.19 / 2024.2.12 / 2025.1.3 or later
Fixed in 2023.3.192024.2.122025.1.3
Interim mitigation

Upgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to patch the path traversal vulnerability in the file upload functionality.

Recommended fix High confidence

Tableau Server 2025.1.3 (or 2024.2.12, or 2023.3.19 - choose the release branch appropriate for your environment)

  1. 1. Identify the current Tableau Server version by checking the server or using Tableau Server Administration commands
  2. 2. Review the Tableau Server upgrade documentation for your current version to ensure compatibility
  3. 3. Backup the Tableau Server repository database and all content (workbooks, data sources, flows) before proceeding
  4. 4. Download the appropriate fixed version from the Salesforce/Tablet download portal: 2025.1.3, 2024.2.12, or 2023.3.19
  5. 5. Run the Tableau Server installer/upgrade executable on the primary node
  6. 6. If running a distributed environment, upgrade the primary node first, then each additional node in the cluster
  7. 7. Verify the upgrade completed successfully by checking the Tableau Server status and version
  8. 8. Test that file upload functionality in the tabdoc API is working correctly
Caveat Review release notes for your upgrade path; major version upgrades may introduce changes to workbook compatibility, REST API behavior, or require repository database migration

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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