Clerk-js vulnerable to bypass of OAuth authentication flow by manipulating request at OTP verification stage

published 2025-11-20 11mo ago modified 2025-11-21 11mo ago also CVE-2025-63700

cvss: 7.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

An issue was discovered in Clerk-js 5.88.0 allowing attackers to bypass the OAuth authentication flow by manipulating the request at the OTP verification stage.

Is GHSA-3mm3-wfpv-q85g in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	@clerk/clerk-js	<=5.88.0	no fix listed

Classification

Weakness

CWE-290 Authentication Bypass by Spoofing
CWE-639 Authorization Bypass Through User-Controlled Key

References

nvd.nist.gov /vuln/detail/CVE-2025-63700
advisory
clerk.com
web
github.com /clerk/javascript
package
github.com /itsnishat08/CVE-2025-63700
web

Sources

GitHub Advisory GHSA-3mm3-wfpv-q85g

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.