CVE-2018-19135
ClipperCMS 1.3.3 does not have CSRF protection on its kcfinder file upload (enabled by default).
Does this matter?
A public exploit is published in Exploit-DB and the impact is high, while EPSS rates exploitation at 3.0%. Anyone can run this; patch or mitigate before the next change window and check exposed instances for signs of use.
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 · 87th percentile
- Public exploits
- 1 in Exploit-DB · first 13 November 2018
- CISA KEV
- Not listed
- Weakness
- CWE-352
- Affected
- clippercms/clippercms
- Source
- cve@mitre.org
EPSS 3.0% since 27 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
Public exploits (1)
Entries in Exploit-DB that cite this CVE. Links go to the Exploit-DB page and to the file in the public repository; nothing is hosted here. A verified tick means the Exploit-DB team confirmed the exploit works against the stated version.
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, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.