# CVE-2026-14558: WP User Frontend < 4.3.10 - Editor+ PHP Object Injection via AI Form Builder

> Editors can inject PHP objects via AI Form Builder, potentially leading to remote code execution if a POP chain exists.

- **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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-j5mw-m2j3-5747

## What is CVE-2026-14558?

CVE-2026-14558 is a high-severity unsafe deserialization vulnerability in Unknown User Frontend, published on 28 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The User Frontend  WordPress plugin before 4.3.10 does not properly validate field type definitions and deserialises user-controlled post metadata when rendering submitted posts, allowing users with Editor-level access and above to inject arbitrary PHP objects, which can lead to remote code execution when a suitable POP chain is present on the site.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-14558 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14558 is a high-severity unsafe deserialization vulnerability in Unknown User Frontend, published on 28 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14558 in the wild and no public exploit code.

Affected product: Unknown User Frontend. 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-14558/ (Markdown: https://insights.sbomify.com/CVE-2026-14558/index.md)
```

## Sources

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

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