dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-48149

HIGH · 8.1 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Budibase is an open-source low-code platform. Prior to 3.39.0, the Budibase Text component renders markdown by assigning marked.parse(markdown) straight to innerHTML with no sanitizer (packages/bbui/src/Markdown/MarkdownViewer.svelte:22). Any column a builder binds to a Text component in Markdown mode is a stored-XSS sink writable by every BASIC app user with WRITE on the underlying table. This vulnerability is fixed in 3.39.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Budibase versions prior to 3.39.0 contain a stored XSS vulnerability in the Text component's Markdown mode. The MarkdownViewer component at packages/bbui/src/Markdown/MarkdownViewer.svelte:22 directly assigns marked.parse(markdown) output to innerHTML without any sanitization, allowing attackers with WRITE permissions on underlying tables to inject malicious scripts that execute when the markdown is rendered.

MitigationUpgrade Budibase to version 3.39.0 or later, which implements proper sanitization of markdown output before rendering to innerHTML. Alternatively, restrict WRITE permissions on tables until the upgrade is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Budibase version
    Check the installed Budibase version by reviewing package.json, docker image tags, or the Budibase admin console about page. Compare against the affected range: versions prior to 3.39.0.
    Affected if The installed version is below 3.39.0.
  2. Locate Text components in Markdown mode
    Review Budibase applications and identify any Text components configured to use Markdown mode. This can be done by inspecting app definitions or UI component settings.
    Affected if Text components set to Markdown rendering mode are present in any application.
  3. Check table WRITE permissions
    Examine permissions on tables that serve as data sources for the Markdown Text components. Determine if users (particularly non-admin users) have WRITE or higher permissions on these tables.
    Affected if Users have WRITE permissions on tables that feed data to Markdown Text components.
  4. Verify vulnerability exposure
    Confirm that the MarkdownViewer component at packages/bbui/src/Markdown/MarkdownViewer.svelte is being used. This is the component that directly assigns marked.parse(markdown) output to innerHTML without sanitization.
    Affected if The MarkdownViewer component renders user-contributed or table-sourced content in Markdown mode.

A user is affected if running Budibase below version 3.39.0 AND using Text components in Markdown mode that display content from tables where users have WRITE permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Budibase to version 3.39.0 or later, which implements proper sanitization of markdown output before rendering to innerHTML. Alternatively, restrict WRITE permissions on tables until the upgrade is applied.

Recommended fix High confidence

3.39.0

  1. Upgrade Budibase to version 3.39.0 or later. For self-hosted deployments, update your Budibase installation to the latest release.
  2. If using a specific package manager or deployment method, ensure the bbui package (packages/bbui) is updated to the version that includes the fix.
  3. After upgrading, verify that the MarkdownViewer component properly sanitizes markdown content before rendering.
  4. Test that the Text component in Markdown mode no longer executes malicious scripts stored in table data.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48149 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data