NocoDB up to 2026.05.0 spreadsheet-import Endpoint confused deputy
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.73 |
Summary
A vulnerability has been found in NocoDB up to 2026.05.0 and classified as critical. Affected by this issue is some unknown functionality of the component spreadsheet-import Endpoint. This manipulation causes confused deputy. This vulnerability appears as CVE-2026-53931. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability classified as critical was found in NocoDB up to 2026.05.0. Affected by this vulnerability is an unknown part of the component spreadsheet-import Endpoint. The manipulation with an unknown input leads to a confused deputy vulnerability. The CWE definition for the vulnerability is CWE-441. The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-import endpoint axiosRequestMake could be used as a generic HTTP proxy. Before the fix it was reachable unauthenticated, and its URL-extension allowlist was a regex tested against the full URL string, so URLs whose query string ended in .csv satisfies the gate even though the underlying request is for another file. This vulnerability is fixed in 2026.05.1.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-53931 since 06/11/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
Upgrading to version 2026.05.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
Website
- Product: https://github.com/nocodb/nocodb/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Confused deputyCWE: CWE-441
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: NocoDB 2026.05.1
Timeline
06/11/2026 CVE reserved06/23/2026 Advisory disclosed
06/23/2026 VulDB entry created
06/23/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-hmcr-rmjq-47qr
Status: Confirmed
CVE: CVE-2026-53931 (🔒)
GCVE (CVE): GCVE-0-2026-53931
GCVE (VulDB): GCVE-100-373033
Entry
Created: 06/23/2026 23:47Changes: 06/23/2026 23:47 (66)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.