PatchTheCVElucidcms vulnerabilities
Recent CVEs affecting lucidcms products. 4 tracked.
lucidcms has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-04-06. Highest priority: CVE-2005-3130 (score 48/100).
- CVE-2006-1635 MEDIUM 5.0 DOWNGRADE LucidCMS 2.0.0 RC4 allows remote attackers to obtain sensitive information via a direct request to /lucid_phpl
- CVE-2006-1634 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in index.php in LucidCMS 2.0.0 RC4 allows remote attackers to inject
- CVE-2005-3130 HIGH 7.5 DOWNGRADE SQL injection vulnerability in lucidCMS 1.0.11 allows remote attackers to execute arbitrary SQL commands via t
- CVE-2005-3127 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in index.php in lucidCMS 1.0.11 allows remote attackers to inject arb
FAQ
How do I fix lucidcms 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 lucidcms being exploited right now?
None of the tracked lucidcms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which lucidcms CVE should I patch first?
CVE-2005-3130 currently ranks highest (48/100): SQL injection vulnerability in lucidCMS 1.0.11 allows remote attackers to execute arbitrary SQL commands via t.