CVE-2026-41478: Saltcorn: SQL Injection via Unparameterized Sync Endpoints (maxLoadedId)

Should you act?

Critical, preconditions apply

Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
• EPSS 0.4%, percentile 37: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 37% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Only applies if your dependency tree includes @saltcorn/server (npm) < 1.4.6, fixed in 1.4.6; @saltcorn/server (npm) >= 1.5.0-beta.0, < 1.5.6, fixed in 1.5.6; @saltcorn/server (npm) >= 1.6.0-alpha.0, < 1.6.0-beta.5, fixed in 1.6.0-beta.5. Check your lockfile, including transitive dependencies.

What it is

Saltcorn is an extensible, open source, no-code database application builder. Prior to 1.4.6, 1.5.6, and 1.6.0-beta.5, a SQL injection vulnerability in Saltcorn’s mobile-sync routes allows any authenticated low-privilege user with read access to at least one table to inject arbitrary SQL through sync parameters. This can lead to full database exfiltration, including admin password hashes and configuration secrets, and may also enable database modification or destruction depending on the backend. This vulnerability is fixed in 1.4.6, 1.5.6, and 1.6.0-beta.5.

From the GitHub advisory

Summary A critical SQL injection vulnerability in Saltcorn’s mobile-sync routes allows any authenticated low-privilege user with read access to at least one table to inject arbitrary SQL through sync parameters. This can lead to full database exfiltration, including admin password hashes and configuration secrets, and may also enable database modification or destruction depending on the backend.

Details The issue affects the mobile-sync endpoints:

- POST /sync/loadchanges - POST /sync/deletes

According to the provided analysis, user-controlled values from the request body are interpolated directly into SQL template literals without parameterization, type enforcement, or sanitization. In particular, req.body.syncInfos[tableName].maxLoadedId is embedded into SQL in getSyncRows() and timestamp-derived values are similarly interpolated in getDelRows().

Relevant vulnerable code paths include:

Weakness type: CWE-89.

Product: @saltcorn/server (npm) · Assigned by: GitHub_M · Published: 2026-04-24

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: low (any account)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.44% probability of exploitation activity in the next 30 days; percentile 37.

Timeline

• 2026-04-16 — GitHub-reviewed advisory GHSA-jp74-mfrx-3qvh published (critical)
• 2026-04-24 — CVE record published by GitHub_M
• 2026-04-27 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-jp74-mfrx-3qvh github.com
2. CVE.org record CVE-2026-41478 cve.org
3. NVD entry CVE-2026-41478 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com

Critical npm advisories · Today’s Security Digest