Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

Saltcorn Server allows logged-in users to delete arbitrary files because of a path traversal vulnerability

CVE-2024-47818GHSA-43f3-h63w-p6f6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@saltcorn/server 1.0.0-beta.16), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-47818: 0.78% estimated exploitation activity in the next 30 days; percentile 56.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A logged-in user with any role can delete arbitrary files on the filesystem by calling the sync/cleansyncdir endpoint. The dirname POST parameter is not validated/sanitized and is used to construct the syncDir that is deleted by calling fs.rm. Details - file: https://github.com/saltcorn/saltcorn/blob/v1.0.0-beta.15/packages/server/routes/sync.js#L337-L346 PoC The following PoC can be executed with a user with any role (admin, staff, user, public) - create a file in a folder different from where the server is started: - log with a user and retrieve valid connect.sid and csrf values - send the following curl request - check if the file previously created does not exist anymore: obtain connect.sid and csrf values A possible way to retrieve connect.sid and csrf values is to use the password reset functionality: - log in - open the browser developer console, go to the Network tab filter for settings request - visit http://localhost:3000/auth/settings - trigger the change password…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-43f3-h63w-p6f6

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-43f3-h63w-p6f6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-47818

Advisory: Saltcorn Server allows logged-in users to delete arbitrary files because of a path traversal vulnerability
IDs: CVE-2024-47818, GHSA-43f3-h63w-p6f6
Record: https://patchnext.com/advisories/cve-2024-47818 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @saltcorn/server 1.0.0-beta.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @saltcorn/server: affected <= 1.0.0-beta.15; fixed in 1.0.0-beta.16

## Suggested inspection (read-only)
- `npm ls @saltcorn/server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @saltcorn/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-43f3-h63w-p6f6 (OSV record GHSA-43f3-h63w-p6f6 lists affected ranges: npm @saltcorn/server >=0 <1.0.0-beta.16 (fixed))
- Verified: https://github.com/advisories/GHSA-43f3-h63w-p6f6 (GitHub-reviewed advisory GHSA-43f3-h63w-p6f6 lists affected ranges: npm @saltcorn/server >=0 <=1.0.0-beta.15)

Commands are suggestions: review each one before running it.

Loading voting…