How severe is GHSA-rcph-x7mj-54mm?

No CVSS score has been assigned to GHSA-rcph-x7mj-54mm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rcph-x7mj-54mm?

GHSA-rcph-x7mj-54mm affects the following packages: nocodb (npm). Ecosystems affected: npm.

How do I fix GHSA-rcph-x7mj-54mm?

Update nocodb to 0.301.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcph-x7mj-54mm is resolved across your whole dependency graph.

How do I detect GHSA-rcph-x7mj-54mm 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-rcph-x7mj-54mm 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-rcph-x7mj-54mm?

O3 pinpoints whether GHSA-rcph-x7mj-54mm 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-rcph-x7mj-54mm actively exploited in the wild?

No public exploit code has been indexed for GHSA-rcph-x7mj-54mm 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 type of vulnerability is GHSA-rcph-x7mj-54mm?

GHSA-rcph-x7mj-54mm is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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-rcph-x7mj-54mm published, and has it been updated?

GHSA-rcph-x7mj-54mm was published on March 3, 2026 and was last updated on March 4, 2026. 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-rcph-x7mj-54mm

GHSA-rcph-x7mj-54mm is a Cross-site Scripting (XSS) vulnerability in nocodb. O3 Security confirms whether GHSA-rcph-x7mj-54mm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

NocoDB Vulnerable to Stored Cross-site Scripting via Comments

Also known asCVE-2026-28397

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

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

nocodbnpm

2Kdownloads / week

Description

Summary

Comments rendered via v-html without sanitization, enabling stored XSS.

Details

Comments in Comments.vue were parsed by markdown-it with html: true and injected via v-html without DOMPurify. A user with Commenter role can inject arbitrary HTML that executes for all viewers.

Impact

Stored XSS — malicious scripts execute for any user viewing the comment.

Credit

This issue was discovered by an AI agent developed by the GitHub Security Lab and reviewed by GHSL team members @p- (Peter Stockli) and @m-y-mo (Man Yue Mo).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`nocodb`	all versions	0.301.3

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.301.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcph-x7mj-54mm 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-rcph-x7mj-54mm 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-rcph-x7mj-54mm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Comments rendered via `v-html` without sanitization, enabling stored XSS. ### Details Comments in `Comments.vue` were parsed by markdown-it with `html: true` and injected via `v-html` without DOMPurify. A user with Commenter role can inject arbitrary HTML that executes for all viewers. ### Impact Stored XSS — malicious scripts execute for any user viewing the comment. ### Credit This issue was discovered by an AI agent developed by the GitHub Security Lab and reviewed by GHSL team members [@p-](https://github.com/p-) (Peter Stockli) and [@m-y-mo](https://github.com/m-y-mo) (Man

O3 Security · Impact-Aware SCA

Is GHSA-rcph-x7mj-54mm in your dependencies?

O3 detects GHSA-rcph-x7mj-54mm 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