# CVE-2026-5127: Deserialization in User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration

> Authenticated attackers can inject PHP objects via the wpuf_files parameter to execute code or delete files if a POP chain exists.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-jc25-ggg4-hhvw

## What is CVE-2026-5127?

CVE-2026-5127 is a high-severity unsafe deserialization vulnerability in wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Deserialization of Untrusted Data in versions up to, and including, 4.3.1 This is due to insufficient input validation and type checking on the wpuf_files parameter during form submission, combined with unconditional deserialization via maybe_unserialize() when displaying post content. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary PHP objects, which can be leveraged to execute arbitrary code, delete arbitrary files, or perform other malicious actions if a POP chain is present on the target system.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-5127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5127 is a high-severity unsafe deserialization vulnerability in wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5127 in the wild and no public exploit code.

Affected product: wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration. 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-5127/ (Markdown: https://insights.sbomify.com/CVE-2026-5127/index.md)
```

## Sources

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

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