lucidcrew vulnerabilities
Recent CVEs affecting lucidcrew products. 6 tracked.
lucidcrew has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-04-03. Highest priority: CVE-2017-7402 (score 67/100).
- CVE-2017-7402 CRITICAL 9.8 DOWNGRADE Pixie 1.0.4 allows remote authenticated users to upload and execute arbitrary PHP code via the POST data in an
- CVE-2017-7363 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=publish&m=module&x= XSS attack.
- CVE-2017-7362 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=publish&m=dynamic&x= XSS attack.
- CVE-2017-7361 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=publish&m=static&x= XSS attack.
- CVE-2017-7360 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=settings&x= XSS attack.
- CVE-2017-7359 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=login&m= XSS attack.
FAQ
How do I fix lucidcrew vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is lucidcrew being exploited right now?
None of the tracked lucidcrew CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which lucidcrew CVE should I patch first?
CVE-2017-7402 currently ranks highest (67/100): Pixie 1.0.4 allows remote authenticated users to upload and execute arbitrary PHP code via the POST data in an.