# CVE-2022-4680: Revive Old Posts – Social Media Auto Post and Scheduling Plugin < 9.0.11 - PHP Object Injection

> Admins can trigger PHP object injection via unsafe deserialization in settings, potentially leading to code execution if gadgets exist.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2023
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-pqm2-5wmp-22wm

## What is CVE-2022-4680?

CVE-2022-4680 is a high-severity unsafe deserialization vulnerability in Unknown Revive Old Posts, published on 30 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Revive Old Posts WordPress plugin before 9.0.11 unserializes user input provided via the settings, which could allow high privilege users such as admin to perform PHP Object Injection when a suitable gadget is present.

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

It affects 1 product.


Products: Revive Revive Old Posts.

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

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

## Is CVE-2022-4680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4680 is a high-severity unsafe deserialization vulnerability in Unknown Revive Old Posts, published on 30 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4680 exists.

Affected product: Unknown Revive Old Posts. 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-4680/ (Markdown: https://insights.sbomify.com/CVE-2022-4680/index.md)
```

## Sources

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

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