How severe is GHSA-387m-j3p9-3php?

No CVSS score has been assigned to GHSA-387m-j3p9-3php yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-387m-j3p9-3php?

GHSA-387m-j3p9-3php affects the following packages: nocodb (npm). Ecosystems affected: npm.

How do I fix GHSA-387m-j3p9-3php?

Update nocodb to 0.301.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-387m-j3p9-3php is resolved across your whole dependency graph.

How do I detect GHSA-387m-j3p9-3php in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nocodb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-387m-j3p9-3php 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-387m-j3p9-3php?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-387m-j3p9-3php can be triaged on real exposure rather than presence alone.

Is GHSA-387m-j3p9-3php actively exploited in the wild?

No public exploit code has been indexed for GHSA-387m-j3p9-3php 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-387m-j3p9-3php?

GHSA-387m-j3p9-3php has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th 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-387m-j3p9-3php?

GHSA-387m-j3p9-3php is classified as CWE-204 (CWE-204). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-387m-j3p9-3php?

A Nuclei detection template exists for GHSA-387m-j3p9-3php, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-387m-j3p9-3php published, and has it been updated?

GHSA-387m-j3p9-3php was published on March 2, 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

Not in CISA KEV

GHSA-387m-j3p9-3php — nocodb

GHSA-387m-j3p9-3php is a CWE-204 vulnerability in nocodb. A fix is available for nocodb — see the affected versions and patch details below.

NocoDB Vulnerable to User Enumeration via Password Reset Endpoint

Also known asCVE-2026-28358

Published

Mar 2, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-387m-j3p9-3php.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

nocodbnpm

2Kdownloads / week

Description

Summary

The password forgot endpoint returned different responses for registered and unregistered emails, allowing user enumeration.

Details

POST /api/v2/auth/password/forgot returned a success message for registered emails but 'Your email has not been registered.' for unknown emails. The fix returns a uniform response regardless of whether the email exists.

Impact

An unauthenticated attacker can determine whether an email is registered. No credentials or data are exposed.

Credit

This issue was reported by @Tulgaaaaaaaa.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`nocodb`	all versions	0.301.3`npm install nocodb@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nocodb to 0.301.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-387m-j3p9-3php 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-387m-j3p9-3php can be triaged on real exposure rather than presence alone.

Tailored to GHSA-387m-j3p9-3php. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect GHSA-387m-j3p9-3php

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-387m-j3p9-3php -u https://target

Template: NocoDB - User Enumeration
Severity: medium
Impact: Attackers can enumerate registered users, potentially aiding further targeted attacks.
Remediation: Update to version 0.301.3 or later.

Template by ProjectDiscovery nuclei-templates (DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Summary The password forgot endpoint returned different responses for registered and unregistered emails, allowing user enumeration. ### Details `POST /api/v2/auth/password/forgot` returned a success message for registered emails but `'Your email has not been registered.'` for unknown emails. The fix returns a uniform response regardless of whether the email exists. ### Impact An unauthenticated attacker can determine whether an email is registered. No credentials or data are exposed. ### Credit This issue was reported by [@Tulgaaaaaaaa](https://github.com/Tulgaaaaaaaa).

O3 Security · Impact-Aware SCA

Is GHSA-387m-j3p9-3php in your dependencies?

O3 Security finds GHSA-387m-j3p9-3php across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works