What is GHSA-9237-RG5P-RHFW?

GHSA-9237-RG5P-RHFW is a high-severity incorrect authorization vulnerability in @saltcorn/data (npm), affecting versions < 1.4.4. It is fixed in 1.4.4, 1.5.2, 1.6.0-beta.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

Which versions of @saltcorn/data are affected by GHSA-9237-RG5P-RHFW?

@saltcorn/data (npm) versions < 1.4.4 is affected.

Is there a fix for GHSA-9237-RG5P-RHFW?

Yes. GHSA-9237-RG5P-RHFW is fixed in 1.4.4, 1.5.2, 1.6.0-beta.2. Upgrade to this version or later.

Is GHSA-9237-RG5P-RHFW exploitable, and should I be worried?

Whether GHSA-9237-RG5P-RHFW 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-9237-RG5P-RHFW 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-9237-RG5P-RHFW in @saltcorn/data

Q: Which versions of @saltcorn/data are affected by GHSA-9237-RG5P-RHFW?

@saltcorn/data (npm) versions < 1.4.4 is affected.

Q: Is there a fix for GHSA-9237-RG5P-RHFW?

Yes. GHSA-9237-RG5P-RHFW is fixed in 1.4.4, 1.5.2, 1.6.0-beta.2. Upgrade to this version or later.

Q: Is GHSA-9237-RG5P-RHFW exploitable, and should I be worried?

Whether GHSA-9237-RG5P-RHFW 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-9237-RG5P-RHFW 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-9237-RG5P-RHFW?

Upgrade: @saltcorn/data to 1.4.4 or later, @saltcorn/data to 1.5.2 or later, @saltcorn/data to 1.6.0-beta.2 or later.

Summary

@saltcorn/data: Tenant user role is used for tenant creation role check

When a tenant admin is logged out of the root domain (e.g., saltcorn.com) but logged in to their own tenant space as admin, they can simply append /tenant/create to their tenant URL. The system reads the role from the tenant context (admin), and a new tenant is created on the root domain (in PUBLIC SCHEMA > _sc_tenants), rather than in the tenant's own _sc_tenants table.

If the same logic applies to other routes, a tenant admin effectively gains admin rights on the root domain.

PoC

A tenant-created subtenant appears under the Saltcorn public schema instead of the tenant's own schema.

Even when role_id=1 is required for tenant creation on saltcorn.com (only admin can create tenants), existing tenant admins can still create new tenants because their local role_id:1 is evaluated against the root domain.
Even when role_to_create_tenant is set to 0 in the tenant's _sc_config schema, or removed entirely, the tenant admin can still create sub-tenants on the root domain, suggesting role_to_create_tenant is not being read at all.

Impact

Tenant admins gain unauthorized admin-level access to the root domain. Any authenticated tenant admin can perform privileged operations (e.g., creating tenants) on the root domain by exploiting the role context mismatch.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Affected versions

@saltcorn/data (< 1.4.4) @saltcorn/data (>= 1.5.0-beta.0, < 1.5.2) @saltcorn/data (>= 1.6.0-alpha.0, < 1.6.0-beta.2)

Security releases

@saltcorn/data → 1.4.4 (npm) @saltcorn/data → 1.5.2 (npm) @saltcorn/data → 1.6.0-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 the following packages to resolve this vulnerability:

@saltcorn/data to 1.4.4 or later; @saltcorn/data to 1.5.2 or later; @saltcorn/data to 1.6.0-beta.2 or later

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

Frequently Asked Questions

What is GHSA-9237-RG5P-RHFW? GHSA-9237-RG5P-RHFW is a high-severity incorrect authorization vulnerability in @saltcorn/data (npm), affecting versions < 1.4.4. It is fixed in 1.4.4, 1.5.2, 1.6.0-beta.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
Which versions of @saltcorn/data are affected by GHSA-9237-RG5P-RHFW? @saltcorn/data (npm) versions < 1.4.4 is affected.
Is there a fix for GHSA-9237-RG5P-RHFW? Yes. GHSA-9237-RG5P-RHFW is fixed in 1.4.4, 1.5.2, 1.6.0-beta.2. Upgrade to this version or later.
Is GHSA-9237-RG5P-RHFW exploitable, and should I be worried? Whether GHSA-9237-RG5P-RHFW 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-9237-RG5P-RHFW 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-9237-RG5P-RHFW?
- Upgrade @saltcorn/data to 1.4.4 or later
- Upgrade @saltcorn/data to 1.5.2 or later
- Upgrade @saltcorn/data to 1.6.0-beta.2 or later

Other vulnerabilities in @saltcorn/data

CVE-IDSeverityPackage summary

GHSA-59XV-588H-2VMMLow@saltcorn/data: @saltcorn/data vulnerable to SQL Injection via jsexprToSQL Literal Handler