Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

p4cms vulnerabilities and fixes

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

p4cms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-09-13. Highest priority: CVE-2006-4769 (score 53/100).

FAQ

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

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

Which p4cms CVE should I patch first?

CVE-2006-4769 currently ranks highest (53/100): PHP remote file inclusion vulnerability in abf_js.php in p4CMS 1.05 allows remote attackers to execute arbitra.

← Back to latest CVEs