CVE-2026-28360: 
JavaScript vulnerability analysis and mitigation

Overview

CVE-2026-28360 is a plaintext password storage vulnerability in NocoDB, an open-source platform for building databases as spreadsheets. Shared view passwords were stored unhashed in the nc_views database table and compared using direct string equality (!==), rather than a secure hashing mechanism. All NocoDB versions up to and including 0.301.2 (npm package) are affected. The vulnerability was disclosed on March 2, 2026, and carries a CVSS v3.1 score of 5.3 (Medium) and a CVSS v4.0 score of 2.7 (Low) (GitHub Advisory, NocoDB Advisory).

Technical details

The root cause is classified as CWE-256 (Plaintext Storage of a Password). The password column in the nc_views database table stored shared view passwords in cleartext, and verification logic across public-datas.service.ts, public-metas.service.ts, and calendar-datas.service.ts used direct string equality comparison (!==) rather than a constant-time cryptographic comparison of hashed values. This design flaw means that any attacker who gains read access to the NocoDB database can immediately retrieve all shared view passwords in plaintext. Additionally, the use of non-constant-time string comparison introduces a theoretical timing side-channel that could allow password guessing attacks (NocoDB Advisory, GitHub Advisory).

Impact

The primary impact is a confidentiality breach: if the NocoDB database is compromised, all shared view passwords are immediately readable in plaintext, enabling unauthorized access to any password-protected shared views and the data they expose. The risk is further amplified by password reuse scenarios, where the same password may protect other systems or accounts. There is no direct integrity or availability impact from this vulnerability itself, but unauthorized access to shared views could expose sensitive business data stored within NocoDB (NocoDB Advisory).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time (GitHub Advisory). The vulnerability requires prior database access to exploit, which significantly limits the attack surface. The EPSS score is approximately 0.044% (14th percentile), indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no threat actor attribution has been reported.

Exploitation steps

  1. Gain database access: Obtain read access to the NocoDB backend database (e.g., SQLite, MySQL, or PostgreSQL) through a separate vulnerability, misconfiguration, credential theft, or insider access.
  2. Query the nc_views table: Execute a SQL query such as SELECT id, title, password FROM nc_views WHERE password IS NOT NULL; to retrieve all shared views that have passwords set.
  3. Retrieve plaintext passwords: Since passwords are stored unhashed, the query results directly yield usable plaintext credentials for each password-protected shared view.
  4. Access protected shared views: Use the retrieved passwords to authenticate to any NocoDB shared view URL, gaining unauthorized access to the data contained within those views.
  5. Attempt password reuse: Test the recovered passwords against other services or accounts associated with the same users, as the advisory notes that risk is amplified in password reuse scenarios (NocoDB Advisory).

Indicators of compromise

  • Database: Unexpected or unauthorized queries against the nc_views table, particularly SELECT statements targeting the password column; review database audit logs if enabled.
  • Logs: Unusual authentication attempts against shared view URLs, especially from unfamiliar IP addresses or at unusual times; NocoDB application logs showing repeated access to password-protected shared views.
  • Network: Anomalous outbound connections from the database server; unexpected database client connections from non-application hosts.

Mitigation and workarounds

Upgrade NocoDB to version 0.301.3 or later, which patches this vulnerability by implementing proper password hashing for shared view passwords (NocoDB Release). After upgrading, rotate all shared view passwords to ensure previously exposed plaintext values are no longer valid. As an interim measure prior to patching, restrict database access to only authorized application accounts and audit database access logs for any unauthorized queries against the nc_views table (NocoDB Advisory).

Community reactions

The vulnerability was responsibly reported by researcher @Tulgaaaaaaaa and was addressed as part of a broader security fix release (0.301.3) that acknowledged multiple researchers including contributors from GitHub Security Lab and bugbunny.ai (NocoDB Release). No significant broader media coverage or notable community commentary beyond the standard advisory publication has been identified.

Additional resources


Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

GHSA-gvwc-5hr5-44p8HIGH7.5
  • JavaScript logoJavaScript
  • probe-image-size
NoYesOct 26, 2026
GHSA-5jh3-w3fj-6758LOW3.7
  • JavaScript logoJavaScript
  • probe-image-size
NoYesOct 26, 2026
GHSA-5v8x-rm7w-m4c7LOW3.7
  • JavaScript logoJavaScript
  • probe-image-size
NoYesOct 26, 2026
GHSA-7pqp-3q23-mwr8LOW3.7
  • JavaScript logoJavaScript
  • probe-image-size
NoYesOct 26, 2026
GHSA-3qg4-7mq2-gm93MEDIUMN/A
  • JavaScript logoJavaScript
  • probe-image-size
NoYesOct 26, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management