Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

pgmarket vulnerabilities and fixes

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

pgmarket has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-08-14. Highest priority: CVE-2006-4115 (score 44/100).

FAQ

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

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

Which pgmarket CVE should I patch first?

CVE-2006-4115 currently ranks highest (44/100): PHP remote file inclusion vulnerability in common.inc.php in PgMarket 2.2.3, when register_globals is enabled,.

← Back to latest CVEs