# CVE-2026-7647: Profile Builder Pro <= 3.14.5 - Unauthenticated PHP Object Injection

> Unauthenticated attackers can achieve code execution via PHP object injection in the Profile Builder Pro WordPress plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-9ppp-7g47-4h53

## What is CVE-2026-7647?

CVE-2026-7647 is a high-severity unsafe deserialization vulnerability in Cozmoslabs Profile Builder Pro, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Profile Builder Pro plugin for WordPress is vulnerable to PHP Object Injection in all versions up to and including 3.14.5. This is due to the use of PHP's maybe_unserialize() function on the attacker-controlled 'args' POST parameter within the wppb_request_users_pins_action_callback() AJAX handler, which lacked any nonce verification, type checking, or input validation before deserialization. Because the handler was registered with both wp_ajax_ and wp_ajax_nopriv_ hooks, it was reachable by completely unauthenticated users. This makes it possible for unauthenticated attackers to inject arbitrary PHP objects into application memory.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-7647 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7647 is a high-severity unsafe deserialization vulnerability in Cozmoslabs Profile Builder Pro, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7647 in the wild and no public exploit code.

Affected product: Cozmoslabs Profile Builder Pro. 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-7647/ (Markdown: https://insights.sbomify.com/CVE-2026-7647/index.md)
```

## Sources

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

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