GHSA-726g-59wr-cj4c
@budibase/server: Command Injection in PostgreSQL Dump Command
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
@budibase/serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Location: packages/server/src/integrations/postgres.ts:529-531
Description
The PostgreSQL integration constructs shell commands using user-controlled configuration values (database name, host, password, etc.) without proper sanitization. The password and other connection parameters are directly interpolated into a shell command.
Code Reference
const dumpCommand = `PGPASSWORD="${
this.config.password
}" pg_dump --schema-only "${dumpCommandParts.join(" ")}"`
Attack Vector
An attacker who can control database configuration values (e.g., through compromised credentials or configuration injection) can inject shell commands. For example:
- Password:
password"; malicious-command; echo " - Database name:
db"; rm -rf /; echo "
Impact
- Remote code execution
- System compromise
- Data exfiltration
Recommendation
- Use environment variables for sensitive values instead of command-line arguments
- Validate and sanitize all configuration values
- Use proper escaping for shell arguments
- Consider using a PostgreSQL library's native dump functionality instead of shell commands
Example Fix
import { execFile } from "child_process"
import { promisify } from "util"
const execFileAsync = promisify(execFile)
// Use execFile with proper argument handling
const env = {
...process.env,
PGPASSWORD: this.config.password
}
const args = [
"--schema-only",
"--host", this.config.host,
"--port", this.config.port.toString(),
"--username", this.config.user,
"--dbname", this.config.database
]
try {
const { stdout } = await execFileAsync("pg_dump", args, { env })
return stdout
} catch (error) {
// Handle error
}
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @budibase/server | all versions | 3.23.32 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @budibase/server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @budibase/server to 3.23.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-726g-59wr-cj4c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-726g-59wr-cj4c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-726g-59wr-cj4c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-726g-59wr-cj4c in your dependencies?
O3 detects GHSA-726g-59wr-cj4c across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.