Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

projectcms vulnerabilities and fixes

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

projectcms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-05-01. Highest priority: CVE-2009-1500 (score 44/100).

FAQ

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

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

Which projectcms CVE should I patch first?

CVE-2009-1500 currently ranks highest (44/100): SQL injection vulnerability in index.php in ProjectCMS 1.0 Beta allows remote attackers to execute arbitrary S.

← Back to latest CVEs