What is GHSA-WXF3-4FVJ-VQQX?

GHSA-WXF3-4FVJ-VQQX is a high-severity security vulnerability in @saltcorn/cli (npm), affecting versions < 0.8.8-beta.2. It is fixed in 0.8.8-beta.2.

How severe is GHSA-WXF3-4FVJ-VQQX?

GHSA-WXF3-4FVJ-VQQX has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @saltcorn/cli are affected by GHSA-WXF3-4FVJ-VQQX?

@saltcorn/cli (npm) versions < 0.8.8-beta.2 is affected.

Is there a fix for GHSA-WXF3-4FVJ-VQQX?

Yes. GHSA-WXF3-4FVJ-VQQX is fixed in 0.8.8-beta.2. Upgrade to this version or later.

Is GHSA-WXF3-4FVJ-VQQX exploitable, and should I be worried?

Whether GHSA-WXF3-4FVJ-VQQX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-WXF3-4FVJ-VQQX is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-WXF3-4FVJ-VQQX in @saltcorn/cli

Q: How severe is GHSA-WXF3-4FVJ-VQQX?

GHSA-WXF3-4FVJ-VQQX has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @saltcorn/cli are affected by GHSA-WXF3-4FVJ-VQQX?

@saltcorn/cli (npm) versions < 0.8.8-beta.2 is affected.

Q: Is there a fix for GHSA-WXF3-4FVJ-VQQX?

Yes. GHSA-WXF3-4FVJ-VQQX is fixed in 0.8.8-beta.2. Upgrade to this version or later.

Q: Is GHSA-WXF3-4FVJ-VQQX exploitable, and should I be worried?

Whether GHSA-WXF3-4FVJ-VQQX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-WXF3-4FVJ-VQQX is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-WXF3-4FVJ-VQQX?

Upgrade @saltcorn/cli to 0.8.8-beta.2 or later.

Summary

Unsafe plugins can be installed via pack import by tenant admins

Unsafe plugins (for instance sql-list) can be installed in subdomain tenants via pack import even if unsafe plugin installation for tenants is disables

Details

I have an example
https://bot20230704.saltcorn.com/view/all_plugins
It's publicly accessible (but has not so secure values except list of tenants).
But using this mech one can read any data from other tenants.

Revived after 0.8.7

After patch in 0.8.7 this is not fixed completely.

Here are steps to reproduce:

Publish to NPM plugin that was not approved by admin (in case of saltcorn.com) by @glutamate. I've just published this one: https://www.npmjs.com/package/saltcorn-qrcode
Publish somewhere plugin store that includes plugin from previous step: https://gist.github.com/pyhedgehog/f1fd7cb13f4d0a7ccf6a965748d19bd2
Add plugin store link to tenant store.
Install plugin.
Use it in tenant: https://bot20230704.saltcorn.com/view/testqr_show/1

Here are logic:
Unsafe plugins checked against this list:
https://github.com/saltcorn/saltcorn/blob/99fe277e497fd193bb070acd8c663aa254a9907c/packages/server/load_plugins.js#L191
But it's under control of tenant admin, not server admin.
Proposed login:

const safes = getRootState().getConfig("available_plugins",[]).filter(p=>!p.unsafe).map(p=>p.location);

Impact

All tenants of installation (i.e. saltcorn.com), can be compromised from tenant user has admin access. If an untrusted user has admin rights to a tenant instance, they will be able to install a plug-in that can access information from other tenants

GHSA-WXF3-4FVJ-VQQX has a CVSS score of 8.7 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.8.8-beta.2); upgrading removes the vulnerable code path.

Affected versions

@saltcorn/cli (< 0.8.8-beta.2)

Security releases

@saltcorn/cli → 0.8.8-beta.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade @saltcorn/cli to 0.8.8-beta.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-WXF3-4FVJ-VQQX? GHSA-WXF3-4FVJ-VQQX is a high-severity security vulnerability in @saltcorn/cli (npm), affecting versions < 0.8.8-beta.2. It is fixed in 0.8.8-beta.2.
How severe is GHSA-WXF3-4FVJ-VQQX? GHSA-WXF3-4FVJ-VQQX has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @saltcorn/cli are affected by GHSA-WXF3-4FVJ-VQQX? @saltcorn/cli (npm) versions < 0.8.8-beta.2 is affected.
Is there a fix for GHSA-WXF3-4FVJ-VQQX? Yes. GHSA-WXF3-4FVJ-VQQX is fixed in 0.8.8-beta.2. Upgrade to this version or later.
Is GHSA-WXF3-4FVJ-VQQX exploitable, and should I be worried? Whether GHSA-WXF3-4FVJ-VQQX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-WXF3-4FVJ-VQQX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-WXF3-4FVJ-VQQX? Upgrade @saltcorn/cli to 0.8.8-beta.2 or later.