Home
» Security vulnerabilities
» CVE-2023-5104
Improper Input Validation in GitHub repository nocodb/nocodb prior to 0.96.0.
NVD Status: Modified ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2023-5104
Conclusion & alert: CVE-2023-5104 is rated High Exploit Risk (67.2/100) : CVSS Medium severity, with medium exploitation likelihood (EPSS 0.82%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Public exploit references (Exploit-DB) for CVE-2023-5104
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2023-5104
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-02-13
0.51%
0.82%
+0.30%
2
2025-11-21
0.36%
0.51%
+0.15%
3
2025-11-18
—
0.36%
—
Full EPSS history
(15 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2023-5104
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
6.5
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8
3.6
[email protected]
5.7
3.0
MEDIUM
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.1
3.6
[email protected]
Weakness enumeration for CVE-2023-5104
GitHub Security Advisory for CVE-2023-5104
GHSA-xrpm-hccg-28x7 · Severity: medium · Ecosystem: npm
— Improper Input Validation in nocodb
Affected software / configurations for CVE-2023-5104
Vendor
Product
Version
Raw CPE
nocodb
nocodb
< 0.96.0
cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*
References for CVE-2023-5104
cvelogic
Threat Intelligence