Budibase: Unrestricted Upload of File with Dangerous Type
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Budibase | budibase | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Budibase | Budibase |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-82rc-gxrg-v4gf | Budibase: Unrestricted Upload of File with Dangerous Type |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.175% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Budibase
Budibase budibase |
|
| Vendors & Products |
Budibase
Budibase budibase |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Budibase is an open-source low-code platform. Prior to 3.38.2, the file upload endpoint POST /api/attachments/process does not enforce active-content restrictions for authenticated users. The checks for dangerous file extensions are conditionally wrapped inside if (isPublicUser) or if (isPublicUser || !env.SELF_HOSTED), meaning any authenticated builder can upload executable web content — SVG files with inline <script> tags, HTML pages with JavaScript, .js modules — which are then stored in the object store (MinIO/S3) with their correct MIME types. When the resulting signed URL is opened by any app user, the browser executes the payload. Impact is persistent stored XSS over all application end users. This vulnerability is fixed in 3.38.2. | |
| Title | Budibase: Unrestricted Upload of File with Dangerous Type | |
| Weaknesses | CWE-434 CWE-79 |
|
| References |
| |
| Metrics |
cvssV3_1
|