dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-52450

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Salesforce Tableau Server on Windows, Linux (abdoc 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

Absolute path traversal vulnerability in Tableau Server's abdoc API create-data-source-from-file-upload modules allows attackers to specify arbitrary file paths during file uploads, potentially writing files to unintended locations on the server filesystem.

MitigationApply vendor patches: upgrade to Tableau Server 2025.1.3 or later, 2024.2.12 or later, or 2023.3.19 or later to remediate 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Determine installed Tableau Server version
    Run 'tsm version' from the command line on the Tableau Server, or check the Tableau Server About page via the web interface (Help > About Tableau Server), or query the version from the PostgreSQL repository database.
    Affected if The installed version is less than 2023.3.19, or between 2024.2.0 and 2024.2.11 inclusive, or between 2025.1.0 and 2025.1.2 inclusive.
  2. Verify the abdoc API is accessible
    Check if the /abdoc/ API endpoints are exposed on the Tableau Server by reviewing the Tableau Server's web server configuration or attempting a localized HTTP request to common abdoc paths such as /api/3.12/abdoc or similar upload-related endpoints (actual path may vary).
    Affected if The abdoc API endpoints are publicly or internally accessible without additional restrictions.
  3. Confirm file upload functionality is enabled
    Review Tableau Server's site settings and configuration for data source upload capabilities. Check whether users with appropriate permissions can upload .tds or .twb files through the UI or API.
    Affected if File upload for data sources is permitted for any authenticated or unauthenticated users.
  4. Inspect server filesystem permissions
    Check the permissions on the Tableau Server's data directories (typically C:\ProgramData\Tableau\Tableau Server\data\tabsvc\files\ on Windows or /var/opt/tableau/tableau_server/data/tabsvc/files/ on Linux) to determine if the process user has write access outside intended directories.
    Affected if The Tableau Server process user has write access to directories outside the designated upload folder.

You are affected if your Tableau Server version falls within the vulnerable ranges AND the abdoc API file upload modules are accessible and enabled.

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

Apply vendor patches: upgrade to Tableau Server 2025.1.3 or later, 2024.2.12 or later, or 2023.3.19 or later to remediate 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 depending on compatibility with your environment)

  1. Review the Tableau Server upgrade documentation at help.salesforce.com for your current version
  2. Ensure system prerequisites are met for the target version (2025.1.3, 2024.2.12, or 2023.3.19 depending on your upgrade path)
  3. Back up the Tableau Server repository database and configuration files
  4. Stop all Tableau Server services before beginning the upgrade
  5. Download the appropriate Tableau Server installer for your target fixed version from the Tableau website
  6. Run the installer with administrator privileges
  7. Follow the on-screen upgrade wizard prompts, selecting the upgrade option
  8. Verify all services start correctly after upgrade
Caveat Review release notes for your target version for any breaking changes; upgrading across multiple major versions may require additional migration steps

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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