# CVE-2026-66047: ProfilePress WordPress Plugin < 4.17.2 Unauthenticated Arbitrary Plugin Installation RCE

> Unauthenticated attackers can achieve remote code execution by brute-forcing a weak token to install arbitrary plugins in ProfilePress.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-7p89-vxx8-4q67, UBUNTU-CVE-2026-66047

## What is CVE-2026-66047?

CVE-2026-66047 is a critical authentication bypass vulnerability in Proper Fraction ProfilePress, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ProfilePress (wp-user-avatar) WordPress plugin before 4.17.2 contains an unauthenticated remote code execution vulnerability that allows unauthenticated attackers to install and activate arbitrary plugins by brute-forcing a weak 32-bit connect token via the ppress_connect_process AJAX handler. Attackers can supply a caller-controlled URL through the file request parameter to trigger silent plugin installation and activation, achieving PHP code execution as the web-server user.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-66047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66047 is a critical authentication bypass vulnerability in Proper Fraction ProfilePress, published on 31 Aug 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-66047 in the wild and no public exploit code.

Affected product: Proper Fraction ProfilePress. 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-66047/ (Markdown: https://insights.sbomify.com/CVE-2026-66047/index.md)
```

## Sources

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

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