CVE-2022-32430 json
Hardcoded JWT Token in Lin CMS Spring Boot
published 2022-07-21 4 y ago modified 2026-06-17 4 mo ago also GHSA-q72p-4w56-hx7h , EUVD-2022-6395
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.0%
- EPSS 5.0% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
An access control issue in Lin CMS Spring Boot v0.2.1 allows attackers to access the backend information and functions within the application.
Exploit prediction
5.04% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Lin CMS Spring Boot - Default JWT Token nuclei detection template
- mesec.cn https://www.mesec.cn/archives/278 referenced PoC, tagged "exploit" by a source, unverified
- mesec.cn https://www.mesec.cn/archives/277 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| 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 |
|---|---|---|---|
| maven | io.github.talelin:lin-cms-core | <=0.2.1 |
no fix listed |
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
mesec.cn
/archives/278
exploit, third-party-advisory
-
mesec.cn
/archives/277
exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-32430
advisory
-
github.com
/TaleLin/lin-cms-spring-boot
package
-
github.com
/TaleLin/lin-cms-spring-boot/blob/3fc25bd8c10c73db2e7230809b322127eac554e3/src/main/resources/application.yml#
web
-
web.archive.org
/web/20220721190946/https://www.mesec.cn/archives/277
web
Sources
- CVE List CVE-2022-32430
- GitHub Advisory GHSA-q72p-4w56-hx7h
- NVD CVE-2022-32430
Fencer Vulns 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.