CVE-2026-41478
Received
Received - Intake
BaseFortify
Publication date: 2026-04-24
Last updated on: 2026-04-28
Assigner: GitHub, Inc.
Description
Description
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.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | 1.6.0 |
| saltcorn | saltcorn | to 1.4.6 (exc) |
| saltcorn | saltcorn | From 1.5.0 (inc) to 1.5.6 (exc) |
| saltcorn | saltcorn | 1.6.0 |
Helpful Resources
Exploitability
CWE
KEV
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70