External risk intelligence

NocoDB Stored Cross-Site Scripting Vulnerability Allows Account Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130716

NocoDB is a web-based database management platform commonly deployed as an internet-facing or intranet-facing web application. Since it functions as a web interface for data management, it is often accessible via standard web browsers in networked environments, making the application's interface a common point of interaction for users.

Cross-site Scripting

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability affects NocoDB, a web-based database management tool, allowing authenticated users to potentially hijack accounts by injecting malicious scripts. The core issue lies in how the application processes user-provided input within its formula rendering, which could enable attackers to steal sensitive session information from other users. The main concern is confirming relevance and exposure to your deployed instances.

  • Malicious scripts can be injected into database fields.
  • Attackers can steal session tokens and take over accounts.
  • Confirm relevance and exposure for deployed instances.

Attack Path

How an attacker could exploit the issue

An attacker with Creator or Editor access can inject malicious markup into fields that are processed by URL() formulas. This markup is then rendered without proper sanitization by the canvas grid, potentially leading to the theft of session tokens from localStorage and unauthorized account takeover.

  • Authenticated access required.
  • Inject markup into formula fields.
  • Session token theft and account takeover.

Live Threat

Current exploitation, exposure, and threat context

A stored cross-site scripting vulnerability in NocoDB could allow authenticated users with Creator or Editor roles to execute arbitrary scripts. This occurs when unsanitized markup injected into fields is rendered through URL() formulas, potentially leading to session token theft when other users view the affected table.

  • User session tokens.
  • Injecting malicious markup into fields.
  • Account takeover of viewing users.

Operational Fix

Recommended remediation, mitigation, and detection steps

The NocoDB platform's stored cross-site scripting vulnerability impacts authenticated users with Creator or Editor roles, posing a risk of account takeover. Application owners, in conjunction with platform or infrastructure teams, should prioritize identifying all NocoDB instances, assessing their exposure and business criticality, and then planning remediation or mitigation strategies.

  • Identify NocoDB instances and ownership.
  • Verify user roles and reachability.
  • Plan remediation or mitigation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is NocoDB?

NocoDB is a web-based database management platform that transforms databases into intelligent spreadsheets. It provides a visual interface for teams to interact with, manage, and collaborate on data. Users often deploy it to simplify database administration through a browser-based dashboard, which acts as the central hub for data operations within an organization.

What does CVE-2026-130716 mean?

This is a stored Cross-Site Scripting (XSS) vulnerability, classified as CWE-79. It occurs when a web application saves untrusted data and displays it to users without proper cleaning. In this case, the application improperly renders data from formula fields, which allows malicious code to execute inside the browsers of other users who view the same table.

How can an attacker trigger this NocoDB bug?

An attacker needs an existing Creator or Editor account to exploit this. They must inject malicious markup into a database field that uses a URL() formula. If an attacker only has Viewer access, or if they do not have the permissions to modify these specific formula-driven fields, the vulnerability cannot be triggered through this path.

Is my NocoDB instance relevant to this threat?

According to Halo Surface Signal, NocoDB is frequently deployed as an internet-facing web application, which increases the likelihood of unauthorized interaction. You should consider your instance relevant if it is accessible over a network where users with Creator or Editor roles interact with database tables, as these roles are required to input the malicious markup.

What should I do to address this vulnerability?

First, locate all running NocoDB instances and verify who has administrative or editor-level access within them. Assess the business criticality of the data hosted on these instances to prioritize your response. Once identified, work with your infrastructure or platform teams to plan for software updates or risk mitigation steps to prevent unauthorized script execution.

References