Pixie 1.0.4 allows remote authenticated users to upload and execute arbitrary PHP code via the POST data in an admin/index.php?s=publish&x=filemanager request for a filename with a double extension, such as a .jpg.php file with Content-Type of image/jpeg.
Product
lucidcrew pixie vulnerabilities
9 published CVES affecting lucidcrew pixie, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 1
- High
- 1
- Medium
- 7
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest lucidcrew pixie CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 5.0%
-
MediumCVSS 6.1
Pixie 1.0.4 allows an admin/index.php s=publish&m=module&x= XSS attack.
-
MediumCVSS 6.1
Pixie 1.0.4 allows an admin/index.php s=publish&m=dynamic&x= XSS attack.
-
MediumCVSS 6.1
Pixie 1.0.4 allows an admin/index.php s=publish&m=static&x= XSS attack.
-
MediumCVSS 6.1
Pixie 1.0.4 allows an admin/index.php s=settings&x= XSS attack.
-
MediumCVSS 6.1
Pixie 1.0.4 allows an admin/index.php s=login&m= XSS attack.
-
MediumCVSS 4.3
Multiple cross-site scripting (XSS) vulnerabilities in the contact module (admin/modules/contact.php) in Pixie CMS 1.04 allow remote attackers to inject arbitrary web script or HTML via the (1) uemail or (2) subject parameter in the Contact form to contact/.
-
HighCVSS 7.5 EPSS 1.6%
Multiple SQL injection vulnerabilities in Pixie CMS 1.01 through 1.04 allow remote attackers to execute arbitrary SQL commands via the (1) pixie_user parameter and (2) Referer HTTP header in a request to the default URI.
-
MediumCVSS 5.0
Pixie 1.04 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by admin/modules/static.php and certain other files.
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.