LeptonCMS version 7.3.0 contains an arbitrary file upload vulnerability, which is caused by the lack of proper validation for uploaded files. An authenticated attacker can exploit this vulnerability by uploading a specially crafted ZIP/PHP file to execute arbitrary code.
Product
lepton-cms leptoncms vulnerabilities
8 published CVES affecting lepton-cms leptoncms, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 0
- High
- 5
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest lepton-cms leptoncms CVEs
Newest publication first
-
HighCVSS 8.8 EPSS 0.82%
-
HighCVSS 8.8 EPSS 1.3%
File Upload vulnerability in lepton v.7.1.0 allows a remote authenticated attackers to execute arbitrary code via uploading a crafted PHP file.
-
HighCVSS 8.8 EPSS 1.2%
File Upload vulnerability in lepton v.7.1.0 allows a remote authenticated attackers to execute arbitrary code via uploading a crafted PHP file to the save.php and config.php component.
-
HighCVSS 7.8 EPSS 0.42%
An issue in Lepton CMS v.7.0.0 allows a local attacker to execute arbitrary code via the upgrade.php file in the languages place.
-
HighCVSS 7.2 EPSS 15.6%
An arbitrary file upload vulnerability in LEPTON v7.0.0 allows authenticated attackers to execute arbitrary PHP code by uploading this code to the backend/languages/index.php languages area.
-
MediumCVSS 6.1 EPSS 0.51%
Cross Site Scripting (XSS) vulnerability in backend/pages/modify.php in Lepton-CMS version 4.7.0, allows remote attackers to execute arbitrary code.
-
MediumCVSS 4.8 EPSS 1.7%
Lepton-CMS 4.7.0 is affected by cross-site scripting (XSS). An attacker can inject the XSS payload in the URL field of the admin page and each time an admin visits the Menu-Pages-Pages Overview section, the XSS will be triggered.
-
CVE-2020-12705 Multiple cross-site scripting (XSS) vulnerabilities exist in LeptonCMS before 4.6.0.
PublishedMediumCVSS 6.1 EPSS 0.64%Multiple cross-site scripting (XSS) vulnerabilities exist in LeptonCMS before 4.6.0.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.