Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ClipperCMS 1.3.3 File Upload CSRF Vulnerability #494
This is regarding the ClipperCMS 1.3.3 File Upload CSRF Vulnerability that I already reported by sending a direct email last August 27, 2018 regarding this issue and followed up on September 4, 2018 and September 10, 2018 but haven't received any reply.
ClipperCMS 1.3.3 does not have CSRF protection on its kcfinder file upload which is being used by default. This can be used by an attacker to perform actions for an admin (or any user with file upload capability). With this vulnerability, it can automatically upload file/s (by default it allows aac,au,avi,css,cache,doc,docx,gz,gzip,htm,html,js,mp3,mp4,mpeg,mpg,ods,odp,odt,pdf,ppt,pptx,rar,tar,tgz,txt,wav,wmv,xls,xlsx,xml,z,zip as file types). Note that web shell that can be used for remote code execution can be achieved depending on the file types being accepted. Uploaded file can be accessed publicly on the "/assets/files" directory (e.g. uploaded a malicious html file with filename: poc.html file => http://clipperwebsite/clipper/assets/files/poc.html). This can lead for the website to be host unintended file/s.
Steps to reproduce:
Admin (or user with file upload capability) logged in ClipperCMS 1.3.3 -> browse/open a controlled website with the poc below (e.g. by link or open PoC below in a browser where admin/user logged in to ClipperCMS 1.3.3) -> file is uploaded and can be accessed on http://clipperwebsite/clipper/assets/files/poc.html (where poc.html is the filename of the uploaded file)
Proof of Concept:
PoC below will automatically upload a "poc.html" file with simple XSS payload. Steps above are how to make use of the PoC.
Actual video demo of the ClipperCMS 1.3.3 file upload CSRF vulnerability being exploited: