Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

zapms vulnerabilities

Recent CVEs affecting zapms products. 1 tracked.

zapms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2013-04-12. Highest priority: CVE-2013-3050 (score 49/100).

FAQ

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

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

Which zapms CVE should I patch first?

CVE-2013-3050 currently ranks highest (49/100): SQL injection vulnerability in ZAPms 1.41 and earlier allows remote attackers to execute arbitrary SQL command.

Products

← Back to latest CVEs