# CVE-2024-3070: Last Viewed Posts by WPBeginner <= 1.0.0 - Unauthenticated PHP Object Injection

> Unauthenticated attackers can inject PHP objects via cookies, potentially leading to code execution or data theft if a POP chain exists.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-5hjg-chj2-7wf8

## What is CVE-2024-3070?

CVE-2024-3070 is a critical unsafe deserialization vulnerability in jottlieb Last Viewed Posts by WPBeginner, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Last Viewed Posts by WPBeginner plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.0.0 via deserialization of untrusted input from the LastViewedPosts Cookie. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-3070?


## How do I fix CVE-2024-3070?

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

## Is CVE-2024-3070 being exploited?

There is no known exploitation of CVE-2024-3070 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3070 and fix it if it is affected.

What it is: CVE-2024-3070 is a critical unsafe deserialization vulnerability in jottlieb Last Viewed Posts by WPBeginner, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3070 in the wild and no public exploit code.

Affected product: jottlieb Last Viewed Posts by WPBeginner. 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-2024-3070/ (Markdown: https://insights.sbomify.com/CVE-2024-3070/index.md)
```

## Sources

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

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