# CVE-2025-2563: User Registration & Membership < 4.1.2- Unauthenticated Privilege Escalation

> Unauthenticated attackers can gain admin privileges by setting their account role during registration when the Membership Addon is enabled.

- **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:** 14 Apr 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-jxh5-f52q-732j

## What is CVE-2025-2563?

CVE-2025-2563 is a high-severity vulnerability in Unknown User Registration & Membership, published on 14 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Registration & Membership  WordPress plugin before 4.1.2 does not prevent users to set their account role when the Membership Addon is enabled, leading to a privilege escalation issue and allowing unauthenticated users to gain admin privileges

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

It affects 1 product.


Products: Wpeverest User Registration \& Membership.

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

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

## Is CVE-2025-2563 being exploited?

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

Public exploit code:

- The User Registration & Membership WordPress plugin before 4.1.2 does not prevent users to set their account role when the Membership Addon is enabled, leading to a privilege escalation issue and allowing unauthenticated users to gain admin privileges (github_poc): https://github.com/Nxploited/CVE-2025-2563
- CVE-2025-2563 (github_poc): https://github.com/dokter69/CVE-2025-2563
- WP User Registration and Membership Unauthenticated Privilege Escalation (CVE-2025-2563) (metasploit)
- CVE-2025-2563 PoC (github_poc): https://github.com/ubaydev/CVE-2025-2563
- https://github.com/0axz-tools/CVE-2025-2563-POC (github_poc): https://github.com/0axz-tools/CVE-2025-2563-POC
- User Registration & Membership <= 4.1.1 - Unauthenticated Privilege Escalation (nuclei): http/cves/2025/CVE-2025-2563.yaml

## Other vulnerabilities in Unknown User Registration & Membership

- [CVE-2025-2594](https://insights.sbomify.com/CVE-2025-2594/): User Registration & Membership < 4.1.3 - Authentication Bypass (high 8.1)
- [CVE-2023-27459](https://insights.sbomify.com/CVE-2023-27459/): WordPress User Registration plugin <= 2.3.2.1 - Authenticated PHP Object Injection vulnerability (high 7.4)
- [CVE-2025-39400](https://insights.sbomify.com/CVE-2025-39400/): WordPress User Registration plugin < 4.2.0 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2025-30899](https://insights.sbomify.com/CVE-2025-30899/): WordPress User Registration plugin <= 4.0.3 - Cross Site Scripting (XSS) vulnerability (medium 5.9)
- [CVE-2025-3282](https://insights.sbomify.com/CVE-2025-3282/): Missing authorization in User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2563 is a high-severity vulnerability in Unknown User Registration & Membership, published on 14 Apr 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-2563 exists.

Affected product: Unknown User Registration & Membership. 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-2563/ (Markdown: https://insights.sbomify.com/CVE-2025-2563/index.md)
```

## Sources

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

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