dbcve.org
CWE-185Weakness · CWE-185

CVE-2026-48147

MEDIUM · 6.5 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 →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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.35.4, the buildMatcherRegex() / matches() functions in packages/backend-core/src/middleware/matchers.ts route patterns are compiled into unanchored regular expressions and tested against ctx.request.url, which includes the full query string. The CSRF middleware in the Budibase Worker uses this matching system to decide whether to skip CSRF token validation. An unauthenticated attacker can forge state-changing cross-origin requests against any Worker API endpoint by injecting a public route pattern into the query string, causing the CSRF middleware to skip token validation entirely. This allows actions such as sending admin invites, modifying global configuration, and managing users without a valid CSRF token. This vulnerability is fixed in 3.35.4.

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

The buildMatcherRegex() and matches() functions in Budibase's middleware use unanchored regex patterns to match against ctx.request.url (which includes query strings). The CSRF middleware relies on this matching to determine whether to skip token validation. By injecting a public route pattern into the query string, attackers can bypass CSRF protection entirely and perform state-changing actions like admin invites, user management, and config modifications without a valid token.

MitigationUpgrade to Budibase version 3.35.4 or later. Alternatively, modify the regex matching logic to use anchored patterns and/or separate URL path from query string before matching.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 installation version
    Check your installed Budibase version by examining package.json, a version API endpoint, or the /api/health endpoint response. Compare this version to the fixed version 3.35.4.
    Affected if The installed version is below 3.35.4, indicating the vulnerable code may be present.
  2. Locate the CSRF middleware implementation
    Search the Budibase codebase for files containing 'buildMatcherRegex' or 'matches' functions, typically found in middleware directories related to CSRF or request handling.
    Affected if The CSRF middleware with these functions exists in the installation.
  3. Inspect regex pattern construction in buildMatcherRegex()
    Examine the buildMatcherRegex() function source code to determine whether the generated regex patterns include start (^) and end ($) anchors. Look for patterns that use string concatenation or RegExp construction without anchoring.
    Affected if The regex patterns are unanchored, meaning they can match anywhere within the tested string rather than requiring a full match.
  4. Verify URL matching includes query strings
    Check how the matches() function is invoked - specifically whether it receives ctx.request.url (full URL including query string) rather than just ctx.path or ctx.url.pathname (the path portion only).
    Affected if The matching uses the full URL with query string parameters, allowing attackers to inject patterns via query parameters.
  5. Confirm CSRF middleware uses this matching for token validation skip
    Review the CSRF middleware code to confirm it calls the pattern matching functions to determine whether to skip token validation for certain routes.
    Affected if The CSRF middleware relies on this vulnerable matching logic to decide whether to enforce CSRF tokens.

You are affected if your Budibase installation is version 3.35.3 or earlier and uses the CSRF middleware with unanchored regex matching against full URLs (including query strings) to bypass token validation.

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 to Budibase version 3.35.4 or later. Alternatively, modify the regex matching logic to use anchored patterns and/or separate URL path from query string before matching.

Recommended fix High confidence

Budibase 3.35.4

  1. Upgrade Budibase to version 3.35.4 or later to remediate this vulnerability.
  2. Verify the upgrade was successful by checking the Budibase version after deployment.
  3. Confirm that the CSRF middleware is now correctly validating tokens for all state-changing requests, including those with query strings.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48147 — 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-48147 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