How severe is GHSA-qg73-g3cf-vhhh?

GHSA-qg73-g3cf-vhhh has a CVSS score of 5.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qg73-g3cf-vhhh?

GHSA-qg73-g3cf-vhhh affects the following packages: nocodb (npm). Ecosystems affected: npm.

How do I fix GHSA-qg73-g3cf-vhhh?

Update nocodb to 0.202.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg73-g3cf-vhhh is resolved across your whole dependency graph.

How do I detect GHSA-qg73-g3cf-vhhh in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nocodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qg73-g3cf-vhhh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qg73-g3cf-vhhh?

O3 pinpoints whether GHSA-qg73-g3cf-vhhh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qg73-g3cf-vhhh actively exploited in the wild?

No public exploit code has been indexed for GHSA-qg73-g3cf-vhhh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qg73-g3cf-vhhh?

GHSA-qg73-g3cf-vhhh has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qg73-g3cf-vhhh?

GHSA-qg73-g3cf-vhhh is classified as Cross-site Scripting (XSS) (CWE-79), Unrestricted File Upload (CWE-434). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-qg73-g3cf-vhhh published, and has it been updated?

GHSA-qg73-g3cf-vhhh was published on May 13, 2024 and was last updated on August 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-qg73-g3cf-vhhh

MEDIUM

NocoDB Allows Preview of Files with Dangerous Content

Also known asCVE-2023-50717

Published

May 13, 2024

Updated

Aug 21, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk43th percentile-0.28%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

nocodbnpm

3Kdownloads / week

Description

Summary

Attacker can upload a html file with malicious content. If user tries to open that file in browser malicious scripts can be executed leading Stored XSS(Cross-Site Script) attack.

PoC

NocoDB was configured using the Release Binary Noco-macos-arm64, and nocodb version 0.202.9 (currently the latest version) was used. binary hash infos: md5(164b727f287af56168bc16fba622d0b4) / sha256(43e8e97f4c5f5330613abe071a359f84e4514b7186f92954b678087c37b7832e) <img width="665" alt="image" src="https://user-images.githubusercontent.com/86613161/287472673-aeb60a02-2080-429f-8583-9f130ab62779.png">

1. Run the binary to start the server and access the arbitrary table dashboard.

Here, used the default Features table.

2. Click `+` in the table `field header` to add an `attachment` field.

3. Click the `Add File(s)` button to select and upload files.

Here, test.html containing <script>alert(document.domain)</script> was uploaded.

4. Check the uploaded file path.

<img width="1163" alt="image" src="https://user-images.githubusercontent.com/86613161/287473337-b1c7c781-2fb5-4bd0-b464-dbd3d4158f04.png"

5. Access the uploaded file path.

When the file path is accessed, the <script>alert(document.domain)</script> script statement contained in the file is executed and the server host appears in the alert message.

Impact

This allows remote attacker to execute JavaScript code in the context of the user accessing the vector. An attacker could have used this vulnerability to execute requests in the name of a logged-in user or potentially collect information about the attacked user by displaying a malicious form.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`nocodb`	≥ 0.202.6&&< 0.202.10	0.202.10

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nocodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update nocodb to 0.202.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg73-g3cf-vhhh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qg73-g3cf-vhhh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qg73-g3cf-vhhh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary --- Attacker can upload a html file with malicious content. If user tries to open that file in browser malicious scripts can be executed leading Stored XSS(Cross-Site Script) attack. ### PoC --- NocoDB was configured using the Release Binary `Noco-macos-arm64`, and nocodb version 0.202.9 (currently the latest version) was used. binary hash infos: md5(164b727f287af56168bc16fba622d0b4) / sha256(43e8e97f4c5f5330613abe071a359f84e4514b7186f92954b678087c37b7832e) <img width="665" alt="image" src="https://user-images.githubusercontent.com/86613161/287472673-aeb60a02-2080-429f-8583-9f130

O3 Security · Impact-Aware SCA

Is GHSA-qg73-g3cf-vhhh in your dependencies?

O3 detects GHSA-qg73-g3cf-vhhh across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works