CVE-2015-2951 json
JWT.php in F21 JWT before 2.0 allows remote attackers to bypass signature verification via crafted tokens.
published 11y ago modified 4mo ago also EUVD-2015-3035
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
JWT.php in F21 JWT before 2.0 allows remote attackers to bypass signature verification via crafted tokens.
Patch / fix
- github.com/F21/jwt@a327cf9 commit
Is CVE-2015-2951 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.75% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
- github.com /F21/jwt/commit/a327cf9052df8f9f97728ca0b5fa78a8231b79b6
-
jvn.jp
/en/jp/JVN06120222/index.html
third-party-advisory, vendor-advisory
-
jvndb.jvn.jp
/jvndb/JVNDB-2015-000073
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/75021
vdb-entry
Sources
- CVE List CVE-2015-2951
- NVD CVE-2015-2951
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.