PatchTheCVECVE-2022-3139: The We’re Open! WordPress plugin before 1.42 does not sanitise and escape some of its settings, which could al
CVE-2022-3139 is a medium-severity flaw (CVSS 4.8) affecting we\'re open. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The We’re Open! WordPress plugin before 1.42 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.8 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | Required |
| EPSS exploit chance | 0.6% (top 50%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2022-10-17 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-3139?
we\'re open: upgrade to 1.42. Exact commands for each OS are on this page.
Is CVE-2022-3139 being exploited?
CVE-2022-3139 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-3139 affect?
CVE-2022-3139 affects we\'re open. Severity is medium (CVSS 4.8). The We’re Open! WordPress plugin before 1.42 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is
How urgent is CVE-2022-3139?
Priority 34/100. Public exploit reference