Advisory

GHSA-44m2-crh7-f4q2

Details, part 2 of 2. The advisory

Details

Initial severity estimate: High (CVSS ~8.1)

Why this is distinct from known CVEs

| CVE / GHSA | Root cause | Different because |
|---|---|---|
| CVE-2026-31818 (SSRF in REST connector) | IMPORT_IP_DENY_LIST not set by default | That fixed HTTP-level filter; SQL driver connections bypass HTTP-layer protection entirely |
| GHSA-2g39-332f-68p9 (RBAC privilege escalation) | Creator role could create Admin roles | Different mechanism — role creation, not route auth bypass |
| GHSA-gw94-hprh-4wj8 (Universal auth bypass) | ?/webhooks/trigger param bypassed auth | Completely different attack primitive |
| GHSA-726g-59wr-cj4c (PostgreSQL dump command injection) | Unsanitized connection params in backup path | Different vector — this is write access to live connection config |

The root cause here is a route-level authorization misconfiguration: PUT /api/datasources/:id is registered in the wrong endpoint group (authorizedRoutes vs builderRoutes).

Fix direction

Move the PUT /api/datasources/:datasourceId route from authorizedRoutes to builderRoutes:

- authorizedRoutes
-   .get("/api/datasources/:datasourceId", datasourceController.find)
-   .put("/api/datasources/:datasourceId", datasourceController.update)

+ authorizedRoutes
+   .get("/api/datasources/:datasourceId", datasourceController.find)

+ builderRoutes
+   .put("/api/datasources/:datasourceId", datasourceController.update)

Submission note

Current state: source-confirmed candidate.
Runtime reproduction (HTTP request against live Budibase instance) has not been executed in this session.
Budibase has an active GHSA process — security reports via GitHub Security Advisories should receive triage within days based on historical pattern.

Sources & licences