PatchTheCVECVE-2022-0680: The Plezi WordPress plugin before 1.0.3 has a REST endpoint allowing unauthenticated users to update the plz_c
CVE-2022-0680 is a medium-severity flaw (CVSS 6.1) affecting plezi. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Plezi WordPress plugin before 1.0.3 has a REST endpoint allowing unauthenticated users to update the plz_configuration_tracker_enable option, which is then displayed in the admin panel without sanitisation and escaping, leading to a Stored Cross-Site Scripting issue
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.9% (top 41%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2022-03-28 |
| 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-0680?
plezi: upgrade to 1.0.3. Exact commands for each OS are on this page.
Is CVE-2022-0680 being exploited?
CVE-2022-0680 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-0680 affect?
CVE-2022-0680 affects plezi. Severity is medium (CVSS 6.1). The Plezi WordPress plugin before 1.0.3 has a REST endpoint allowing unauthenticated users to update the plz_configuration_tracker_enable option, which is then displayed in the admin panel without sanitisation and escaping, leading to a Sto
How urgent is CVE-2022-0680?
Priority 41/100. Public exploit reference