Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

postschedule vulnerabilities and fixes

Recent CVEs affecting postschedule, with upgrade or downgrade steps. 1 tracked.

postschedule has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2008-04-30. Highest priority: CVE-2008-2012 (score 48/100).

FAQ

How do I fix postschedule 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 postschedule being exploited right now?

None of the tracked postschedule CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which postschedule CVE should I patch first?

CVE-2008-2012 currently ranks highest (48/100): SQL injection vulnerability in index.php in the PostSchedule 1.0 module for PostNuke allows remote attackers t.

← Back to latest CVEs