How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

346,508

Total vulnerabilities in the database

@saltcorn/data vulnerable to SQL Injection via jsexprToSQL Literal Handler — @saltcorn / data

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Summary

The jsexprToSQL() function in Saltcorn converts JavaScript expressions to SQL for use in database constraints. The Literal handler wraps string values in single quotes without escaping embedded single quotes, allowing SQL injection when creating Formula-type table constraints.

Vulnerable Component

File: packages/saltcorn-data/models/expression.ts, lines 117-118

Literal({ value }: { value: ExtendedNode }) {
  if (typeof value == &quot;string&quot;) return `&#039;${value}&#039;`;  // NO ESCAPING!
  return `${value}`;
},

Call chain: Formula constraint creation → table_constraints.ts:127 → jsexprToSQL() → Literal() → db.query() executes unsanitized SQL.

Proof of Concept

Injection via Formula Constraint

When an admin creates a Formula-type table constraint with the expression:

name === &quot;test&#039; OR &#039;1&#039;=&#039;1&quot;

The jsexprToSQL() function generates:

(name)=(&#039;test&#039; OR &#039;1&#039;=&#039;1&#039;)

This is then executed as:

ALTER TABLE &quot;tablename&quot; ADD CONSTRAINT &quot;tablename_fml_1&quot; CHECK ((name)=(&#039;test&#039; OR &#039;1&#039;=&#039;1&#039;));

The single quote in the string literal is not escaped, breaking out of the SQL string context.

More Dangerous Payload

name === &quot;&#039;; DROP TABLE users; --&quot;

Generates:

(name)=(&#039;&#039;; DROP TABLE users; --&#039;)

Verified on Saltcorn v1.5.0 (Docker)

Direct invocation of jsexprToSQL() inside the running container confirms the vulnerability:

Input:  name === &quot;hello&quot;
Output: (name)=(&#039;hello&#039;)                          ← Normal

Input:  name === &quot;test&#039; OR &#039;1&#039;=&#039;1&quot;
Output: (name)=(&#039;test&#039; OR &#039;1&#039;=&#039;1&#039;)                ← Single quote NOT escaped, OR injected

Input:  name === &quot;&#039;; DROP TABLE users; --&quot;
Output: (name)=(&#039;&#039;; DROP TABLE users; --&#039;)         ← DROP TABLE injected

The test was performed on a completely fresh Saltcorn installation (zero user-created tables, default Docker setup).

PoC Screenshot

Create a table after moving to the table menu

Go to the table and then to Constraits

Go to Formula

Create a test table for verification

Input the payload and save

Check the table for testing

Impact

Arbitrary SQL execution via crafted CHECK constraints
Data exfiltration through error-based or time-based SQL injection
Database schema manipulation (DROP TABLE, ALTER TABLE)
Potential privilege escalation via direct users table modification

Suggested Remediation

Escape single quotes in the Literal handler:

Literal({ value }: { value: ExtendedNode }) {
  if (typeof value == &quot;string&quot;) return `&#039;${value.replace(/&#039;/g, &quot;&#039;&#039;&quot;)}&#039;`;
  return `${value}`;
},

Alternatively, use parameterized queries for constraint creation instead of string interpolation.

Published: Apr 10, 2026
Updated: Apr 11, 2026
GHSA: GHSA-59xv-588h-2vmm
Severity: Low
Exploit:

CVSS v3:

Severity: Unknown
Score:
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:N

CWEs:

CWE-89

OWASP TOP 10:

A1 - Injection

Affected Software
References

Software	From	Fixed in
@saltcorn / data	-	1.4.5
@saltcorn / data	1.5.0	1.5.5
@saltcorn / data	1.6.0-alpha.0	1.6.0-beta.4

https://github.com/saltcorn/saltcorn/security/advisories/GHSA-59xv-588h-2vmm

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.