CVE-2018-20595 json
Cross-Site Request Forgery (CSRF) in hswebframework.web:hsweb-commons
published 7y ago modified 4mo ago also GHSA-4rm3-4mq4-mfwr , EUVD-2019-0176
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
A CSRF issue was discovered in web/authorization/oauth2/controller/OAuth2ClientController.java in hsweb 3.0.4 because the state parameter in the request is not compared with the state parameter in the session after user authentication is successful.
Patch / fix
Is CVE-2018-20595 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 FencerExploit prediction
0.64% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/hs-web/hsweb-framework/issues/107 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.hswebframework.web:hsweb-commons | <=3.0.4 |
no fix listed |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/hs-web/hsweb-framework/commit/40929e9b0d336a26281a5ed2e0e721d54dd8d2f2
web, patch, third-party-advisory
-
github.com
/hs-web/hsweb-framework/issues/107
web, exploit, issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-20595
advisory
-
github.com
/advisories/GHSA-4rm3-4mq4-mfwr
advisory
-
github.com
/hs-web/hsweb-framework
package
Sources
- CVE List CVE-2018-20595
- GitHub Advisory GHSA-4rm3-4mq4-mfwr
- NVD CVE-2018-20595
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.