Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5amended

@saltcorn/server arbitrary file and directory listing when accessing build mobile app results

GHSA-cfqx-f43m-vfh7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@saltcorn/server 1.0.0-beta.14), 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
5.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary A user with admin permission can read arbitrary file and directory names on the filesystem by calling the admin/build-mobile-app/result?builddirname= endpoint. The builddirname parameter is not properly validated and it's then used to construct the buildDir that is read. The file/directory names under the buildDir will be returned. Details - file: https://github.com/saltcorn/saltcorn/blob/v1.0.0-beta.13/packages/server/routes/admin.js#L2884-L2893 PoC - log into the application as an admin user - visit the following url: http://localhost:3000/admin/build-mobile-app/result?builddirname=/../../../../../../../../ NOTE: it's possible to only see file and directory names but not to download their content. Impact Information disclosure Recommended Mitigation Resolve the buildDir and check if it starts with ${rootFolder.location}/mobileapp.

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

    Amended from ghsa record GHSA-cfqx-f43m-vfh7

  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-cfqx-f43m-vfh7

Agent brief

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

# Patch Next advisory brief: GHSA-cfqx-f43m-vfh7

Advisory: @saltcorn/server arbitrary file and directory listing when accessing build mobile app results
IDs: GHSA-cfqx-f43m-vfh7
Record: https://patchnext.com/advisories/ghsa-cfqx-f43m-vfh7 (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: Medium (CVSS 5.5)
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.14. A vendor fix does not mean a deployment is fixed.

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

## 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-cfqx-f43m-vfh7 (OSV record GHSA-cfqx-f43m-vfh7 lists affected ranges: npm @saltcorn/server >=0 <1.0.0-beta.14 (fixed))
- Verified: https://github.com/advisories/GHSA-cfqx-f43m-vfh7 (GitHub-reviewed advisory GHSA-cfqx-f43m-vfh7 lists affected ranges: npm @saltcorn/server >=0 <=1.0.0-beta.13)

Commands are suggestions: review each one before running it.

Loading voting…