# CVE-2024-47818: Logged-in users with any role can delete arbitrary files in @saltcorn/server

> Logged-in users can delete arbitrary files on the server via an unvalidated parameter in the sync directory cleanup endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2024
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-43f3-h63w-p6f6

## What is CVE-2024-47818?

CVE-2024-47818 is a medium-severity path traversal vulnerability in saltcorn, published on 7 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Saltcorn is an extensible, open source, no-code database application builder. A logged-in user with any role can delete arbitrary files on the filesystem by calling the `sync/clean_sync_dir` endpoint. The `dir_name` POST parameter is not validated/sanitized and is used to construct the `syncDir` that is deleted by calling `fs.rm`. This issue has been addressed in release version 1.0.0-beta16 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-47818?

2 open source packages ship an affected version, including @saltcorn/server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@saltcorn/server` | npm | All versions | 1.0.0-beta.16 |
| `@saltcorn/server` | npm | All versions | 1.0.0-beta.16 |

## How do I fix CVE-2024-47818?

Upgrade @saltcorn/server to 1.0.0-beta.16 or later.

## Is CVE-2024-47818 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47818 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47818 and fix it if it is affected.

What it is: CVE-2024-47818 is a medium-severity path traversal vulnerability in saltcorn, published on 7 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47818 exists.

Affected packages and fixed versions:
- @saltcorn/server (npm): affected all versions; fixed in 1.0.0-beta.16
- @saltcorn/server (npm): affected all versions; fixed in 1.0.0-beta.16

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-2024-47818/ (Markdown: https://insights.sbomify.com/CVE-2024-47818/index.md)
```

## Sources

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

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