# CVE-2026-104932: Search Regex 3.5 - Authenticated (Subscriber+) Remote Code Execution via User Meta Serialized String Corruption

> Authenticated attackers can achieve remote code execution in the Search Regex WordPress plugin via PHP object injection in the replace_all function.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-pg87-gj3v-m4jx

## What is CVE-2026-104932?

CVE-2026-104932 is a high-severity unsafe deserialization vulnerability in johnny5 Search Regex, published on 16 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Search Regex plugin for WordPress is vulnerable to PHP Object Injection in version 3.5 via deserialization of untrusted input in the replace_all function. This allows authenticated attackers, with subscriber-level access and above, to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-104932?


## How do I fix CVE-2026-104932?

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

## Is CVE-2026-104932 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104932 and fix it if it is affected.

What it is: CVE-2026-104932 is a high-severity unsafe deserialization vulnerability in johnny5 Search Regex, published on 16 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-104932 in the wild and no public exploit code.

Affected product: johnny5 Search Regex. 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-2026-104932/ (Markdown: https://insights.sbomify.com/CVE-2026-104932/index.md)
```

## Sources

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

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