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

> Authenticated users can trigger PHP object injection via the prompt_dismiss_notice action, potentially leading to code execution or CSRF attacks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2023
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-2wpw-75c5-m9hx

## What is CVE-2022-4265?

CVE-2022-4265 is a high-severity unsafe deserialization vulnerability in Unknown Replyable, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-4265?

It affects 1 product.


Products: Gopostmatic Replyable.

## How do I fix CVE-2022-4265?

No fix has been published for CVE-2022-4265 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4265 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4265 exists.

## Other vulnerabilities in Unknown Replyable

- [CVE-2015-9411](https://insights.sbomify.com/CVE-2015-9411/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4265 and fix it if it is affected.

What it is: CVE-2022-4265 is a high-severity unsafe deserialization vulnerability in Unknown Replyable, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4265 exists.

Affected product: Unknown Replyable. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4265/ (Markdown: https://insights.sbomify.com/CVE-2022-4265/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4265
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4265
- OSV: https://osv.dev/vulnerability/CVE-2022-4265

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4265/
Summaries are generated and may contain mistakes; the official description above is the record.