# CVE-2025-58051: Nextcloud Tables app allowed to include local file via PhpSpreadsheet when importing a table

> An attacker can read arbitrary server files by specifying local paths during table import in the Nextcloud Tables app.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-wpp5-4w35-pxq6

## What is CVE-2025-58051?

CVE-2025-58051 is a medium-severity path traversal vulnerability in nextcloud security-advisories, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nextcloud Tables allows you to create your own tables with individual columns. Prior 0.7.6, 0.8.8, and 0.9.5, when importing a table, a user was able to specify files on the server and when their format is supported by the used PhpSpreadsheet library they would be included and their content leaked to the user. It is recommended that the Nextcloud Tables app is upgraded to 0.7.6, 0.8.8 or 0.9.5.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow)

## Which versions are affected by CVE-2025-58051?


## How do I fix CVE-2025-58051?

No fix has been published for CVE-2025-58051 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-58051 being exploited?

There is no known exploitation of CVE-2025-58051 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58051 and fix it if it is affected.

What it is: CVE-2025-58051 is a medium-severity path traversal vulnerability in nextcloud security-advisories, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58051 in the wild and no public exploit code.

Affected product: nextcloud security-advisories. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58051/ (Markdown: https://insights.sbomify.com/CVE-2025-58051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58051
- OSV: https://osv.dev/vulnerability/CVE-2025-58051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58051/
Summaries are generated and may contain mistakes; the official description above is the record.