Vulnerability Database · npm · oauth2-server · Version
oauth2-server 2.3.0
2.3.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.1.1.
Critical 0 High 2 Medium 0 Low 0 Unrated 0
-
Released 14 Sep 2014
Licence MIT
Also known from other sources 2
Newer releases 19
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
oauth2-server 2.3.0 vulnerabilities
2 vulnerabilities cover oauth2-server 2.3.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-18924: Code Injection in oauth2-server | 7.5 high | No fix published | 22 Apr 2021 |
| CVE-2020-26938: oauth2-server through 3.1.1 Open Redirect Vulnerability | 7.2 high | No fix published | 30 Aug 2022 |
Looking for another version, or everything Vulert holds for oauth2-server?
Questions
About oauth2-server 2.3.0
Is oauth2-server 2.3.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover oauth2-server 2.3.0: 0 critical, 2 high, 0 medium and 0 low. The upgrade Vulert recommends is 3.1.1, and each entry above names the fixed version to move to.
Which version of oauth2-server should I use instead of 2.3.0?
3.1.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.3.0 the latest release of oauth2-server?
No. 2.3.0 was published 14 Sep 2014, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor oauth2-server for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the oauth2-server version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.