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.
References
Configurations
No configuration.
History
27 May 2026, 19:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/Budibase/budibase/security/advisories/GHSA-82rc-gxrg-v4gf - |
27 May 2026, 18:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-05-27 18:16
Updated : 2026-05-27 19:44
NVD link : CVE-2026-46426
Mitre link : CVE-2026-46426
CVE.ORG link : CVE-2026-46426
JSON object : View
Products Affected
No product.
