PatchTheCVEpostnuke vulnerabilities
Recent CVEs affecting postnuke products. 4 tracked.
postnuke has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2010-05-04. Highest priority: CVE-2010-1713 (score 51/100).
- CVE-2010-1713 HIGH 7.5 DOWNGRADE SQL injection vulnerability in modules.php in PostNuke 0.764 allows remote attackers to execute arbitrary SQL
- CVE-2008-1591 HIGH 7.5 UPGRADE The pnVarPrepForStore function in PostNuke 0.764 and earlier skips input sanitization when magic_quotes_runtim
- CVE-2005-1698 MEDIUM 5.0 DOWNGRADE PostNuke 0.750 and 0.760RC3 allows remote attackers to obtain sensitive information via a direct request to (1
- CVE-2005-1697 MEDIUM 5.0 DOWNGRADE The RSS module in PostNuke 0.750 and 0.760RC2 and RC3 allows remote attackers to obtain sensitive information
FAQ
How do I fix postnuke 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 postnuke being exploited right now?
None of the tracked postnuke CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which postnuke CVE should I patch first?
CVE-2010-1713 currently ranks highest (51/100): SQL injection vulnerability in modules.php in PostNuke 0.764 allows remote attackers to execute arbitrary SQL .