getresponse vulnerabilities and fixes

Q: How do I fix getresponse 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.

Q: Is getresponse being exploited right now?

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

Q: Which getresponse CVE should I patch first?

CVE-2023-0167 currently ranks highest (35/100): The GetResponse for WordPress plugin through 5.5.31 does not validate and escape some of its shortcode attribu.

Recent CVEs affecting getresponse, with upgrade or downgrade steps. 2 tracked.

getresponse has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2023-03-20. Highest priority: CVE-2023-0167 (score 35/100).

CVE-2023-0167 MEDIUM 5.4 UPGRADE The GetResponse for WordPress plugin through 5.5.31 does not validate and escape some of its shortcode attribu
CVE-2022-35277 MEDIUM 5.4 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in GetResponse plugin <= 5.5.20 at WordPress.

FAQ

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

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

Which getresponse CVE should I patch first?

CVE-2023-0167 currently ranks highest (35/100): The GetResponse for WordPress plugin through 5.5.31 does not validate and escape some of its shortcode attribu.

← Back to latest CVEs