Saltcorn Server Stored Cross-Site Scripting (XSS) in event logs page

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Event log data is not properly sanitized leading to stored Cross-Site Scripting (XSS) vulnerability. Details - file: https://github.com/saltcorn/saltcorn/blob/v1.0.0-beta.13/packages/server/routes/eventlog.js#L445 PoC The following PoC demonstrates how a non-admin user with permission to read/write on a table can inject malicious javascript code that will be executed in the event log admin panel if event logs are enabled. To demonstrate this issue, we need to prepare some components. The following steps should be executed with an admin user. 1. create a table with one column of type string set read/write permission to staff users (just as an example) - visit http://localhost:3000/table/new - create a table with Table name mytablexss and click Create - click Add field to add a field with Label called payload of type String and click Next - leave default values for Attributes and click Next - it should redirect to http://localhost:3000/table/<table-number - under Edit table…

Published by the source

7 Oct 2024, 15:14 UTC

Last modified by the source

7 Oct 2024, 15:14 UTC

Source last checked

26 Oct 2026, 12:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pf56-h9qf-rxq4

2. Revision 2 · amended · 25 Oct 2026

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

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pf56-h9qf-rxq4

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

# Patch Next advisory brief: GHSA-pf56-h9qf-rxq4

Advisory: Saltcorn Server Stored Cross-Site Scripting (XSS) in event logs page
IDs: GHSA-pf56-h9qf-rxq4
Record: https://patchnext.com/advisories/ghsa-pf56-h9qf-rxq4 (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.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.16; 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-pf56-h9qf-rxq4 (OSV record GHSA-pf56-h9qf-rxq4 lists affected ranges: npm @saltcorn/server >=0 <1.0.0-beta.16 (fixed))
- Verified: https://github.com/advisories/GHSA-pf56-h9qf-rxq4 (GitHub-reviewed advisory GHSA-pf56-h9qf-rxq4 lists affected ranges: npm @saltcorn/server >=0 <1.0.0-beta.16)

Commands are suggestions: review each one before running it.