GHSA-XCX6-4F2G-HHGX

Budibase: S3 presigned URL endpoint authorization regression in v3.39.4 allows BASIC users to obtain S3 PutObject presigned URLs

In Budibase v3.39.4, a regression in the authorization level for the S3 attachment upload endpoint allows any BASIC app user to obtain S3 PutObject presigned URLs. The endpoint uses TABLE/WRITE permission level instead of the intended BUILDER level defined in v3.39.3. Additionally, the controller does not pin the target bucket to the datasource's configured bucket, allowing writes to any S3 bucket the stored IAM credentials can access.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

GHSA-XCX6-4F2G-HHGX has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

Already deployed Kodem?

1. Restore the authorized(BUILDER) middleware on the route
2. Add paramResource("datasourceId") to ensure the datasource belongs to the caller's app
3. Pin the S3 bucket to datasource.config.bucket in the controller, ignoring the caller-supplied bucket value

1. What is GHSA-XCX6-4F2G-HHGX? GHSA-XCX6-4F2G-HHGX is a high-severity incorrect authorization vulnerability in @budibase/server (npm), affecting versions <= 3.38.1. No fixed version is listed yet. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is GHSA-XCX6-4F2G-HHGX? GHSA-XCX6-4F2G-HHGX has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @budibase/server are affected by GHSA-XCX6-4F2G-HHGX? @budibase/server (npm) versions <= 3.38.1 is affected.
4. Is there a fix for GHSA-XCX6-4F2G-HHGX? No fixed version is listed for GHSA-XCX6-4F2G-HHGX yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is GHSA-XCX6-4F2G-HHGX exploitable, and should I be worried? Whether GHSA-XCX6-4F2G-HHGX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-XCX6-4F2G-HHGX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-XCX6-4F2G-HHGX? No fixed version is listed yet. In the interim: Keep the dependency up to date. Audit access-control checks to ensure they are applied consistently and cannot be bypassed.

Other vulnerabilities in @budibase/server