we\'re open vulnerabilities and fixes
Recent CVEs affecting we\'re open, with upgrade or downgrade steps. 1 tracked.
Also searched as: we\'reopen.
we\'re open has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2022-10-17. Highest priority: CVE-2022-3139 (score 34/100).
- CVE-2022-3139 MEDIUM 4.8 UPGRADE The We’re Open! WordPress plugin before 1.42 does not sanitise and escape some of its settings, which could al
FAQ
How do I fix we\'re open 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 we\'re open being exploited right now?
None of the tracked we\'re open CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which we\'re open CVE should I patch first?
CVE-2022-3139 currently ranks highest (34/100): The We’re Open! WordPress plugin before 1.42 does not sanitise and escape some of its settings, which could al.