Saltcorn has an Unauthenticated Path Traversal in sync endpoints allows arbitrary file write and directory read

published 2026-04-10 6 mo ago modified 2026-06-17 4 mo ago also GHSA-32pv-mpqg-h292 , EUVD-2026-21517

cvss: 8.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits: 0; none known

Saltcorn is an extensible, open source, no-code database application builder. Prior to 1.4.5, 1.5.5, and 1.6.0-beta.4, the POST /sync/offline_changes endpoint allows an unauthenticated attacker to create arbitrary directories and write a changes.json file with attacker-controlled JSON content anywhere on the server filesystem. The GET /sync/upload_finished endpoint allows an unauthenticated attacker to list arbitrary directory contents and read specific JSON files. This vulnerability is fixed in 1.4.5, 1.5.5, and 1.6.0-beta.4.

Patch / fix

fixed in 2

npm @saltcorn/server 1.4.5, 1.5.5, 1.6.0-beta.4
saltcorn saltcorn 1.4.5, 1.5.5

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 6 mo ago (2026-04-15)

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/saltcorn/saltcorn/security/advisories/GHSA-32pv-mpqg-h292 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
GitHub	3.1	8.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	@saltcorn/server	<1.4.5 >=1.5.0-beta.0, <1.5.5 >=1.6.0-alpha.0, <1.6.0-beta.4	1.4.5 1.5.5 1.6.0-beta.4

Affected products

saltcorn saltcorn

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

github.com /saltcorn/saltcorn/security/advisories/GHSA-32pv-mpqg-h292
web, exploit, mitigation, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-40163
advisory
github.com /saltcorn/saltcorn
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary