dbcve.org
NocodbApplication

CVE-2026-28360

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-02
Fix available
A fix is available. Upgrade to 0.301.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, shared view passwords were stored in plaintext in the database and compared using direct string equality. This issue has been patched in version 0.301.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NocoDB versions prior to 0.301.3 stored shared view passwords in plaintext within the database rather than using proper hashing mechanisms. Additionally, password comparison was performed using direct string equality rather than constant-time comparison, which could potentially expose the application to timing-based attacks.

MitigationUpgrade NocoDB to version 0.301.3 or later to remediate the plaintext password storage vulnerability. Consider rotating shared view passwords as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NocodbApplication
Affected:< 0.301.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed NocoDB version
    Run `nc -v` or check the package.json file in the NocoDB installation directory, or inspect the About page in the NocoDB UI
    Affected if version is lower than 0.301.3
  2. Identify shared view password storage in database
    Connect to the NocoDB database and query tables related to shared views (commonly _nc_shared_views or similar). Look at columns that store password data - check if values appear as plaintext strings rather than hashed values
    Affected if password column contains plaintext strings that can be read directly
  3. Verify password hashing implementation
    Examine the NocoDB source code or configuration files for how shared view passwords are handled. Look for use of bcrypt, argon2, or similar hashing libraries versus raw storage
    Affected if no hashing library is used for shared view passwords or passwords are stored in plaintext format
  4. Check password comparison method
    Examine the authentication logic for shared views in the codebase. Look for use of `===` or `==` operators for password comparison rather than constant-time comparison functions
    Affected if password comparison uses direct string equality operators instead of constant-time comparison

You are affected if NocoDB version is below 0.301.3 and shared view passwords are stored in plaintext in the database or compared using non-constant-time methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.301.3 or later
Fixed in 0.301.3
Interim mitigation

Upgrade NocoDB to version 0.301.3 or later to remediate the plaintext password storage vulnerability. Consider rotating shared view passwords as a precautionary measure.

Recommended fix High confidence

0.301.3

  1. 1. Backup the Nocodb database before performing any upgrade.
  2. 2. Upgrade Nocodb to version 0.301.3 or later.
  3. 3. After upgrading, verify that shared view passwords are now stored using proper hashing (not plaintext).
  4. 4. If existing shared view passwords exist, consider re-saving them to ensure they are hashed with the new implementation.
  5. 5. Verify the application functions correctly after upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nocodb Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28360 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data