dbcve.org
SaltcornApplication

CVE-2026-41478

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 1.4.6 / 1.5.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

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 enables full database exfiltration including admin password hashes and configuration secrets, and may allow database modification or destruction depending on the backend.

MitigationUpgrade Saltcorn to version 1.4.6, 1.5.6, or 1.6.0-beta.5 or later to patch the SQL injection vulnerability in mobile-sync routes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SaltcornApplication
Affected:< 1.4.6>= 1.5.0, < 1.5.6= 1.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Saltcorn version
    Locate the Saltcorn installation directory and check the package.json file, or run 'npm list saltcorn' to see the installed version. Alternatively, check the application's version indicator in the admin UI if accessible.
    Affected if The version number is less than 1.4.6, OR between 1.5.0 and 1.5.5 inclusive, OR exactly 1.6.0 (non-beta)
  2. Confirm mobile-sync routes are active
    Examine the application's route configuration files in the routes directory for any 'mobile-sync' or 'sync' route definitions. Check the main application entry point for mobile-sync middleware or route registration.
    Affected if Mobile-sync routes are defined and loaded in the application
  3. Verify authentication configuration
    Check the authentication settings in the Saltcorn configuration (usually in config files or database). Confirm whether user authentication is enabled and that the user database table exists.
    Affected if User authentication is enabled and at least one user with read access to a table exists in the system
  4. Inspect mobile-sync parameter handling
    Locate the mobile-sync route handler code (typically in routes/mobile-sync.js or similar). Examine how sync parameters are processed and whether they are passed directly to database queries without parameterized preparation.
    Affected if The code shows parameters being directly concatenated into SQL queries without using parameterized queries or input sanitization

You are affected if your installed Saltcorn version is in the vulnerable range (< 1.4.6, 1.5.0-1.5.5, or 1.6.0) AND the mobile-sync feature is enabled AND at least one authenticated user with table read access exists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.6 / 1.5.6 or later
Fixed in 1.4.61.5.6
Interim mitigation

Upgrade Saltcorn to version 1.4.6, 1.5.6, or 1.6.0-beta.5 or later to patch the SQL injection vulnerability in mobile-sync routes.

Recommended fix High confidence

Upgrade to Saltcorn 1.4.6 or 1.5.6 (stable releases); alternatively 1.6.0-beta.5 if you need beta features

  1. 1. Back up your Saltcorn database and application data before upgrading
  2. 2. Identify your current Saltcorn version by checking package.json or running the application
  3. 3. For installations using npm: run `npm install saltcorn@<fixed_version>` where <fixed_version> is 1.4.6 or 1.5.6 (stable releases)
  4. 4. For Docker installations: pull the corresponding fixed version image tag
  5. 5. After upgrading, restart the Saltcorn service
  6. 6. Verify the version upgrade was successful by checking the application version
  7. 7. Test that the mobile-sync functionality works correctly after the upgrade
  8. 8. Confirm the SQL injection vulnerability is resolved by verifying that sync parameters are properly sanitized
Caveat Review the release notes for 1.4.6 and 1.5.6 to check for any breaking changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Saltcorn Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41478 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data