PatchTheCVECVE-2022-4265: The Replyable WordPress plugin before 2.2.10 does not validate the class name submitted by the request when in
CVE-2022-4265 is a high-severity flaw (CVSS 8.8) affecting replyable. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Replyable WordPress plugin before 2.2.10 does not validate the class name submitted by the request when instantiating an object in the prompt_dismiss_notice action and also lacks CSRF check in the related action. This could allow any authenticated users, such as subscriber to perform Object Injection attacks. The attack could also be done via a CSRF vector against any authenticated user
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 57%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2023-03-06 |
| 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-4265?
replyable: upgrade to 2.2.10. Exact commands for each OS are on this page.
Is CVE-2022-4265 being exploited?
CVE-2022-4265 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-4265 affect?
CVE-2022-4265 affects replyable. Severity is high (CVSS 8.8). The Replyable WordPress plugin before 2.2.10 does not validate the class name submitted by the request when instantiating an object in the prompt_dismiss_notice action and also lacks CSRF check in the related action. This could allow any au
How urgent is CVE-2022-4265?
Priority 47/100. High severity; Public exploit reference