# CVE-2025-3292: Missing authorization in User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder

> Unauthenticated attackers can update other users' passwords via insecure direct object reference if they know the user ID and email.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 12 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hc93-f59p-5vw6

## What is CVE-2025-3292?

CVE-2025-3292 is a medium-severity missing authorization vulnerability in wpeverest User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder, published on 12 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.1.3 via the user_registration_update_profile_details() due to missing validation on the 'user_id' user controlled key. This makes it possible for unauthenticated attackers to update other user's passwords, if they have access to the user ID and email.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Wpeverest User Registration \& Membership.

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

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

## Is CVE-2025-3292 being exploited?

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

## Other vulnerabilities in wpeverest User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder

- [CVE-2025-2594](https://insights.sbomify.com/CVE-2025-2594/): User Registration & Membership < 4.1.3 - Authentication Bypass (high 8.1)
- [CVE-2025-2563](https://insights.sbomify.com/CVE-2025-2563/): User Registration & Membership < 4.1.2- Unauthenticated Privilege Escalation (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3292 is a medium-severity missing authorization vulnerability in wpeverest User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder, published on 12 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3292 in the wild and no public exploit code.

Affected product: wpeverest User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder. 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-3292/ (Markdown: https://insights.sbomify.com/CVE-2025-3292/index.md)
```

## Sources

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

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