Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

p4db vulnerabilities and fixes

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

p4db has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2004-12-31. Highest priority: CVE-2004-2735 (score 32/100).

FAQ

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

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

Which p4db CVE should I patch first?

CVE-2004-2735 currently ranks highest (32/100): Cross-site scripting (XSS) vulnerability in P4DB 2.01 and earlier allows remote attackers to inject arbitrary .

← Back to latest CVEs