CVE-2018-19135
ClipperCMS 1.3.3 does not have CSRF protection on its kcfinder file upload (enabled by default).
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.96%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
ClipperCMS 1.3.3 does not have CSRF protection on its kcfinder file upload (enabled by default). This can be used by an attacker to perform actions for an admin (or any user with the file upload capability). With this vulnerability, one can automatically upload files (by default, it allows html, pdf, xml, zip, and many other file types). A file can be accessed publicly under the "/assets/files" directory.
- CVSS 3.0
- 8.8 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 2.96% probability · 86th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-352
- Affected
- clippercms/clippercms
- Source
- cve@mitre.org
References
- https://github.com/ClipperCMS/ClipperCMS/issues/494Exploit, Issue Tracking, Third Party Advisory
- https://www.exploit-db.com/exploits/45839/Exploit, Third Party Advisory, VDB Entry
- https://github.com/ClipperCMS/ClipperCMS/issues/494Exploit, Issue Tracking, Third Party Advisory
- https://www.exploit-db.com/exploits/45839/Exploit, Third Party Advisory, VDB Entry
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.