Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2023-35843 is a high-severity Path Traversal (CWE-22) vulnerability in Nocodb Nocodb. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
NocoDB through version 0.106.0, or alternatively 0.109.1, contains a path traversal vulnerability tracked as CVE-2023-35843 and assigned CWE-22. The flaw resides in the attachment handling code that processes the path parameter on the /download route, enabling an unauthenticated remote attacker to supply crafted input that resolves outside the intended directory and retrieves arbitrary server files. The issue carries a CVSS 3.1 base score of 7.5, reflecting network attack vector, low complexity, and no required privileges or user interaction, with impacts limited to high confidentiality loss.
An attacker can therefore send a single unauthenticated HTTP request that manipulates the path parameter to read sensitive files such as configuration data, source code, or other server content. Because the vulnerability requires no authentication and is reachable over the network, it can be exploited by any party able to reach the NocoDB instance, potentially exposing credentials or intellectual property stored on the host.
Public references, including advisory.dw1.io/60 and the affected attachment controller implementations in the NocoDB repository, document the vulnerable code paths but do not detail specific patch versions or mitigation steps beyond the version bounds already stated in the CVE description. The associated EPSS score remains high, with a current value of 0.9196 and a peak of 0.9237; no material rise from a low baseline is observable in the supplied data.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-39836
Vulnerability Data
NocoDB through 0.106.0 (or 0.109.1) has a path traversal vulnerability that allows an unauthenticated attacker to access arbitrary files on the server by manipulating the path parameter of the /download route. This vulnerability could allow an attacker to access sensitive…
more
files and data on the server, including configuration files, source code, and other sensitive information.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Validates pathnames and filenames to prevent traversal outside intended directories.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.