CVE-2026-122244 json
Budibase: Cross-privilege Stored XSS in the Budibase Builder via broken HTML-escaping in `jsonFormatter.format()` rendered through `{@html}` in the CSP-less Builder origin
published 11d ago modified yesterday also EUVD-2026-131661 , GHSA-r2q3-7m4h-63qg
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
Budibase is an open-source low-code platform. Prior to 3.50.0, a BASIC application user, or an unauthenticated visitor to a public write form, can store markup in a shared external datasource that a builder or administrator later evaluates in any Handlebars binding Preview that surfaces the value, including the Data-section Formula column editor or any binding drawer. jsonFormatter.format() in packages/frontend-core/src/utils/jsonFormatter.ts leaves raw strings and object keys unescaped, while packages/builder/src/components/common/bindings/EvaluationSidePanel.svelte inserts the formatted result as raw HTML. The Handlebars SafeString path preserves the attacker-controlled value, and the Builder origin lacks a Content-Security-Policy that would block the resulting script. This permits stored script execution in the higher-privileged builder or administrator session rather than the writer's own role, allowing privileged Builder API actions and workspace data access. This issue is fixed in versions 3.50.0 and 4.0.0.
Patch / fix
Is CVE-2026-122244 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- yesterday
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-21).
Exploits and checks
- github.com https://github.com/Budibase/budibase/security/advisories/GHSA-r2q3-7m4h-63qg referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @budibase/server | <=3.38.1 |
no fix listed |
Affected products
- Budibase budibase
Classification
References
-
github.com
/Budibase/budibase/commit/5f37fb43728639c540cc7233283f1100e9315424
web
-
github.com
/Budibase/budibase/security/advisories/GHSA-r2q3-7m4h-63qg
exploit, web, advisory
-
github.com
/Budibase/budibase/releases/tag/v3.50.0
web
-
github.com
/Budibase/budibase/releases/tag/v4.0.0
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-122244
advisory
-
github.com
/Budibase/budibase
package
Sources
- CVE List CVE-2026-122244
- GitHub Advisory GHSA-r2q3-7m4h-63qg
- NVD CVE-2026-122244
- Maintainer advisory GHSA-r2q3-7m4h-63qg
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of Budibase/budibase published their own advisory on GitHub. Reviewed sources take precedence over it.