# CVE-2023-28667: Deserialization in Lead Generated WordPress Plugin

> Unauthenticated attackers can achieve remote code execution via insecure deserialization in the Lead Generated WordPress plugin.

- **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:** 22 Mar 2023
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-cmvc-r236-g4fp

## What is CVE-2023-28667?

CVE-2023-28667 is a critical unsafe deserialization vulnerability in Lead Generated WordPress Plugin, published on 22 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Lead Generated WordPress Plugin, version <= 1.23, was affected by an unauthenticated insecure deserialization issue. The tve_labels parameter of the tve_api_form_submit action is passed to the PHP unserialize() function without being sanitized or verified, and as a result could lead to PHP object injection, which when combined with certain class implementations / gadget chains could be leveraged to perform a variety of malicious actions granted a POP chain is also present.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-28667?

It affects 1 product.


Products: Leadgenerated Lead Generated.

## How do I fix CVE-2023-28667?

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

## Is CVE-2023-28667 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28667 and fix it if it is affected.

What it is: CVE-2023-28667 is a critical unsafe deserialization vulnerability in Lead Generated WordPress Plugin, published on 22 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-28667 exists.

Affected product: Lead Generated WordPress Plugin. 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-2023-28667/ (Markdown: https://insights.sbomify.com/CVE-2023-28667/index.md)
```

## Sources

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

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