# CVE-2023-6933: Better Search Replace <= 1.4.4 - Unauthenticated PHP Object Injection

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

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8gwq-mv35-rmmj

## What is CVE-2023-6933?

CVE-2023-6933 is a high-severity unsafe deserialization vulnerability in wpengine Better Search Replace, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Better Search Replace plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.4.4 via deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No 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-2023-6933?

It affects 1 product.


Products: Wpengine Better Search Replace.

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

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

## Is CVE-2023-6933 being exploited?

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

Public exploit code:

- Introduction to CVE-2023-6933 Vulnerability (github_poc): https://github.com/w2xim3/CVE-2023-6933
- https://github.com/Trex96/vulnerable-bsr-lab-CVE-2023-6933 (github_poc): https://github.com/Trex96/vulnerable-bsr-lab-CVE-2023-6933
- Better Search Replace < 1.4.5 - PHP Object Injection (nuclei): http/cves/2023/CVE-2023-6933.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6933 is a high-severity unsafe deserialization vulnerability in wpengine Better Search Replace, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6933 exists.

Affected product: wpengine Better Search Replace. 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-6933/ (Markdown: https://insights.sbomify.com/CVE-2023-6933/index.md)
```

## Sources

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

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