CVE-2022-39305 json
Gin-vue-admin vulnerable to Unrestricted Upload of File with Dangerous Type
published 2022-10-24 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-41795
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Gin-vue-admin is a backstage management system based on vue and gin, which separates the front and rear of the full stack. Versions prior to 2.5.4 contain a file upload ability. The affected code fails to validate fileMd5 and fileName parameters, resulting in an arbitrary file being read. This issue is patched in 2.5.4b. There are no known workarounds.
Patch / fix
- gin-vue-admin_project gin-vue-admin 2.5.4b
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
1.34% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/flipped-aurora/gin-vue-admin/security/advisories/GHSA-wrmq-4v4c-gxp2 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/flipped-aurora/gin-vue-admin/blob/main/server/utils/breakpoint_continue.go referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- flipped-aurora gin-vue-admin
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
github.com
/flipped-aurora/gin-vue-admin/security/advisories/GHSA-wrmq-4v4c-gxp2
exploit, patch, third-party-advisory
-
github.com
/flipped-aurora/gin-vue-admin/blob/main/server/utils/breakpoint_continue.go
exploit, third-party-advisory
Sources
- CVE List CVE-2022-39305
- NVD CVE-2022-39305
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.