Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

perldiver vulnerabilities and fixes

Recent CVEs affecting perldiver, with upgrade or downgrade steps. 2 tracked.

perldiver has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-09-27. Highest priority: CVE-2005-3067 (score 38/100).

FAQ

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

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

Which perldiver CVE should I patch first?

CVE-2005-3067 currently ranks highest (38/100): Cross-site scripting (XSS) vulnerability in perldiver.cgi in PerlDiver 2.x allows remote attackers to inject a.

← Back to latest CVEs