# CVE-2025-34077: WordPress Pie Register Plugin ≤ 3.7.1.4 Authentication Bypass RCE

> Unauthenticated attackers can bypass authentication to impersonate administrators and execute arbitrary code via malicious plugin uploads.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-3r79-62f7-6gcx

## What is CVE-2025-34077?

CVE-2025-34077 is a critical authentication bypass vulnerability in Genetech Solutions WordPress Pie Register Plugin, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability exists in the WordPress Pie Register plugin ≤ 3.7.1.4 that allows unauthenticated attackers to impersonate arbitrary users by submitting a crafted POST request to the login endpoint. By setting social_site=true and manipulating the user_id_social_site parameter, an attacker can generate a valid WordPress session cookie for any user ID, including administrators. Once authenticated, the attacker may exploit plugin upload functionality to install a malicious plugin containing arbitrary PHP code, resulting in remote code execution on the underlying server.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-34077?


## How do I fix CVE-2025-34077?

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

## Is CVE-2025-34077 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34077 exists.

Public exploit code:

-  WordPress Pie Register ≤ 3.7.1.4 - Admin Privilege Escalation (Unauthenticated) (github_poc): https://github.com/MrjHaxcore/CVE-2025-34077
- Poc for Unauthenticated Admin Session Hijack - Pie Register Plugin (≤ 3.7.1.4) (github_poc): https://github.com/0xgh057r3c0n/CVE-2025-34077
- WordPress Plugin Pie Register Auth Bypass to RCE (metasploit)
- Pie Register WordPress Plugin 3.7.1.4 - Authentication Bypass to RCE (exploitdb)
- Exploiting WordPress vulnerabilities (CVE-2025-34077), authentication bypass via cookie injection, and privilege escalation to root. Part of my Cybersecurity Specialization. (github_poc): https://github.com/salimelh94/Web-Penetration-Test
- WordPress Pie Register <= 3.7.1.4 - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-34077.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34077 and fix it if it is affected.

What it is: CVE-2025-34077 is a critical authentication bypass vulnerability in Genetech Solutions WordPress Pie Register Plugin, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34077 exists.

Affected product: Genetech Solutions WordPress Pie Register Plugin. 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-2025-34077/ (Markdown: https://insights.sbomify.com/CVE-2025-34077/index.md)
```

## Sources

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

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