PatchTheCVEslashcode vulnerabilities and fixes
Recent CVEs affecting slashcode, with upgrade or downgrade steps. 6 tracked.
slashcode has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2004-12-31. Highest priority: CVE-2000-1015 (score 47/100).
- CVE-2004-2656 MEDIUM 4.3 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in Slashdot Like Automated Storytelling Homepage (Slash) (
- CVE-2002-1748 HIGH 7.2 DOWNGRADE Unknown vulnerability in Slash 2.1.x and 2.2 through 2.2.2, as used in Slashcode, allows remote authenticated
- CVE-2002-1681 MEDIUM 6.8 DOWNGRADE Cross-site scripting (XSS) vulnerability in Slashcode CVS releases June 17 through July 1 2002 allows remote a
- CVE-2002-0292 LOW 2.6 UPGRADE Cross-site scripting vulnerability in Slash before 2.2.5, as used in Slashcode and elsewhere, allows remote at
- CVE-2001-1535 MEDIUM 4.6 DOWNGRADE Slashcode 2.0 creates new accounts with an 8-character random password, which could allow local users to obtai
- CVE-2000-1015 HIGH 7.5 UPGRADE The default configuration of Slashcode before version 2.0 Alpha has a default administrative password, which a
FAQ
How do I fix slashcode 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 slashcode being exploited right now?
None of the tracked slashcode CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which slashcode CVE should I patch first?
CVE-2000-1015 currently ranks highest (47/100): The default configuration of Slashcode before version 2.0 Alpha has a default administrative password, which a.