Baserow builds rich‑text mention markup by inserting a user's display name directly into a template literal without HTML encoding. A name that contains an escaped double quote terminates the data‑label attribute and the opening tag, allowing an attacker to inject arbitrary <script> tags. When a table that contains the mention is viewed, the rich‑text field renders the unescaped markup via v‑html, causing the embedded script to execute immediately in every member’s browser. Because the payload is stored within the mention, it runs automatically for any workspace member without requiring interaction, enabling malicious code execution or session hijacking for all viewers.

The vulnerability affects Baserow products before version 2.3.0. Any instance using the 2.2.x series, or earlier releases, is susceptible. The flaw originates in the web‑frontend module where the mention renderer is built, and the server accepts the first_name field without sanitisation. Upgrading to Baserow 2.3.0 or later applies the required escaping and fixes the issue.

The CVSS score of 5.3 indicates a moderate severity that balances the limited privilege required (any workspace member can change their own display name) against the impact of executing scripts in a user's browser. EPSS data is not available, and the flaw is not listed in CISA’s KEV catalog, but its ease of exploitation makes it an attractive target for malicious insiders or compromised accounts. The attack vector is a local, low‑privilege user who can set a display name; once the crafted name is visible in a rich‑text field, the payload is delivered automatically to all other workspace members. The bug persists until the user’s name is updated or the mention is removed, providing ongoing risk until remedied.