# Saltcorn Server stored XSS in event logs page

Source: https://junglewise.ai/threats/saltcorn-server-stored-xss-in-event-logs-page-29714f98  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-10-07. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

Severity: low · CVSS 3.1 · Published 2024-10-07

Saltcorn Server is an open-source low-code application framework that manages tables, views, and event logs. A stored cross-site scripting (XSS) vulnerability in the event logs page allows lower-privileged users (e.g., staff) to inject malicious JavaScript that executes when administrators view the affected log entries, potentially compromising admin accounts or sensitive operations.

Technologies: [@saltcorn/server (npm)](https://junglewise.ai/threats/technologies/saltcorn-server). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** Low severity, with a CVSS score of 3.1, published 7 October 2024.

**Which products and versions are affected?** @saltcorn/server (npm) SEMVER:introduced=0,fixed=1.0.0-beta.16.

**Is there a fix for This vulnerability?** Yes. @saltcorn/server (npm): upgrade to 1.0.0-beta.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is This vulnerability attacked?** It is attacked over the network.

**Am I affected?** Check whether you run @saltcorn/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @saltcorn/server (npm): upgrade to 1.0.0-beta.16 or later

  ```sh
  npm install @saltcorn/server@1.0.0-beta.16
  ```


## Technical details

The vulnerability is a stored XSS flaw (CWE-79) in the event log display route (eventlog.js line 445) that fails to sanitize user-supplied payload data before inserting it into HTML. An attacker with table read/write permissions can insert malicious JavaScript (e.g., <svg/onload=alert()>) via table data; when an administrator views the corresponding event log entry, the unescaped payload is rendered as executable code. The attack requires prior application access and event logging to be enabled, but no special privileges are needed to inject the payload. The vulnerability was patched in version 1.0.0-beta.16 by escaping event body content in the log display.

## Affected products

- Saltcorn Server <=1.0.0-beta.13

## Timeline

- 2024-10-07: disclosed
- 2024-10-07: patched: version 1.0.0-beta.16

## References

- [https://github.com/saltcorn/saltcorn/security/advisories/GHSA-pf56-h9qf-rxq4](https://github.com/saltcorn/saltcorn/security/advisories/GHSA-pf56-h9qf-rxq4)
- [https://github.com/saltcorn/saltcorn/commit/3c551261d0e230635774798009951fa83a07cc3a](https://github.com/saltcorn/saltcorn/commit/3c551261d0e230635774798009951fa83a07cc3a)

## Related threats

- [Saltcorn open redirect in login via backslash bypass](https://junglewise.ai/threats/cve-2026-42259-saltcorn-open-redirect-in-login-via-backslash-bypass)
- [Saltcorn reflected XSS and command injection chaining for RCE](https://junglewise.ai/threats/saltcorn-reflected-xss-and-command-injection-chaining-for-rce-91ca3009)
- [Saltcorn Server path traversal in sync endpoint](https://junglewise.ai/threats/cve-2024-47818-saltcorn-server-path-traversal-in-sync-endpoint)
- [Saltcorn Server remote code execution via prototype pollution](https://junglewise.ai/threats/saltcorn-server-remote-code-execution-via-prototype-pollution-4d2c9025)
- [Saltcorn Server arbitrary file and directory listing via build mobile app](https://junglewise.ai/threats/saltcorn-server-arbitrary-file-and-directory-listing-via-build-mobile-9dae5381)