CVE
NocoDB stored XSS in grid view via URL formulas
Affects NocoDB before 2026.08.0 where a URL() formula references a text field whose value is shown in a grid view. Fixed in 2026.08.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.08.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A URL() formula references a text field whose value is shown in a grid view The grid view is rendered by the canvas cell renderer
Summary
NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows authenticated Creator or Editor users to execute script by injecting markup into fields rendered through URL() formulas. The canvas grid renderer assigns unsanitized formula output to innerHTML, letting attackers steal session tokens from localStorage and take over accounts of users viewing the table.
Who should check
Teams running self-hosted NocoDB before 2026.08.0 that use URL() formulas on text fields in grid views
“The canvas cell renderer used for grid views assigned the rendered output of a URL() formula to innerHTML”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
A URL() formula references a text field whose value is shown in a grid view The grid view is rendered by the canvas cell rendererUpgrade to a fixed version: 2026.08.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130716 (NocoDB before 2026.08.0 Stored XSS via URL Formula in Grid View), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130716 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.08.0
Fixed versions: 2026.08.0.
Conditions (all must be true for the bug to be hit):
- A URL() formula references a text field whose value is shown in a grid view (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-wmj9-wfqf-72cw)
- The grid view is rendered by the canvas cell renderer (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-wmj9-wfqf-72cw)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-130716 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130716 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nocodb/nocodb/security/advisories/GHSA-wmj9-wfqf-72cw
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130716
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130716"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- Posted on X by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.08.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-wmj9-wfqf-72cw |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130716 |
| Record | NVD · CVE-2026-130716 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130716
Is CVE-2026-130716 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A URL() formula serialises the referenced text field's value with only parentheses escaped, and the canvas cell renderer used for grid views assigns that output to innerHTML. Script then runs in the NocoDB origin in the browser of users who view the table, and can read the session token from localStorage to take over the account and access or change data the victim can reach.Source: github.com
Which versions are affected by CVE-2026-130716?
nocodb: before 2026.08.0.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.08.0 are in the affected range. The setup involves a URL() formula that references a text field displayed in a grid view, so a reader can check the running version and look for such formulas in grid views of their tables.Source: github.com
How do I fix CVE-2026-130716?
Upgrade NocoDB to 2026.08.0 or later, which is the listed fixed version.Source: github.com