CVE-2017-7951 json
WonderCMS before 2.0.3 has CSRF because of lack of a token in an unspecified context.
published 2017-04-21 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16922
- 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 47%
- public exploits
- 0
- none known
Summary
WonderCMS before 2.0.3 has CSRF because of lack of a token in an unspecified context.
Patch / fix
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
wondercms.com
/forum/viewtopic.php?f=8&p=1684
patch, vendor-advisory
-
github.com
/robiso/wondercms/releases/tag/2.0.3
issue-tracking, patch, third-party-advisory
Sources
- CVE List CVE-2017-7951
- NVD CVE-2017-7951
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.