CVE-2026-76837 Baserow CVE debrief

Who should care

Defenders responsible for Baserow installations, particularly those with user-generated content or rich-text features, should assess exposure and prioritize remediation to prevent exploitation.

Why it matters

CVE-2026-76837 is a stored XSS vulnerability in Baserow that allows an attacker to inject malicious script code, which is then executed by workspace members who view the table. Defenders should prioritize verifying exposure and applying patches or workarounds to prevent exploitation.

• Workspace members may execute stored script code without clicking, potentially leading to unauthorized actions or data exposure
• An attacker can inject malicious script code, which persists until the name is changed or the mentioning row is removed
• Defenders must verify exposure and apply patches or workarounds to prevent exploitation
• Remediation priority is high due to the potential for unauthorized code execution

Technical summary

The vulnerability exists due to the lack of HTML encoding in the rich-text mention markup. An attacker can inject malicious script code by manipulating the first_name value, which is stored verbatim in the PATCH /api/user/account/ endpoint. The mention renderer in web-frontend/modules/core/editor/mention.js then constructs a template literal that places the name into a data-label attribute and the element body unescaped, allowing for XSS exploitation.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or workarounds to prevent exploitation.

Recommended defensive actions

• Verify exposure by checking if the installed version is prior to 2.3.0
• Apply patches or workarounds to prevent exploitation
• Monitor for suspicious activity and implement compensating controls
• Inventory checks for affected versions and prioritize remediation
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation beyond version 2.3.0 being patched.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.