# CVE-2026-76837: Baserow before 2.3.0 Stored Cross-Site Scripting via Rich Text Mention Display Name

> Stored XSS in Baserow allows attackers to execute scripts in other users' browsers via malicious display names in rich-text mentions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** GHSA-6jjx-jh3j-cxqj

## What is CVE-2026-76837?

CVE-2026-76837 is a medium-severity cross-site scripting vulnerability in Baserow, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Baserow interpolates a user's display name into the rich-text mention markup without HTML encoding. PATCH /api/user/account/ stores the first_name value verbatim, and the mention renderer in web-frontend/modules/core/editor/mention.js builds its element with a template literal that places the name into a data-label attribute and the element body unescaped. A name containing a double quote closes that attribute and the opening tag, so following markup lands in the element content. The result is rendered through v-html by the rich-text field components, so any rich-text cell mentioning the account executes the stored script for every workspace member who views the table, without a click. Any workspace member, at the lowest permission level, can set the name and reach every other member of the workspace, and the payload persists until the name is changed or the mentioning row is removed. Version 2.3.0 escapes the value before interpolation.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-76837?


## How do I fix CVE-2026-76837?

No fix has been published for CVE-2026-76837 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76837 being exploited?

There is no known exploitation of CVE-2026-76837 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76837 and fix it if it is affected.

What it is: CVE-2026-76837 is a medium-severity cross-site scripting vulnerability in Baserow, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76837 in the wild and no public exploit code.

Affected product: Baserow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76837/ (Markdown: https://insights.sbomify.com/CVE-2026-76837/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76837
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76837
- OSV: https://osv.dev/vulnerability/CVE-2026-76837

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76837/
Summaries are generated and may contain mistakes; the official description above is the record.