# CVE-2023-2437: UserPro <= 5.1.1 - Authentication Bypass to Administrator

> Unauthenticated attackers can bypass authentication and log in as any user, including administrators, by exploiting insufficient verification in the Facebook login feature.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 22 Nov 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-w6q9-w8cf-jw9p

## What is CVE-2023-2437?

CVE-2023-2437 is a critical authentication bypass vulnerability in UserPro - Community and User Profile WordPress Plugin, published on 22 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The UserPro plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.1.1. This is due to insufficient verification on the user being supplied during a Facebook login through the plugin. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email. An attacker can leverage CVE-2023-2448 and CVE-2023-2446 to get the user's email address to successfully exploit this vulnerability.

Weakness: CWE-287 (Improper Authentication), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2023-2437?

It affects 1 product.


Products: Userproplugin Userpro.

## How do I fix CVE-2023-2437?

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

## Is CVE-2023-2437 being exploited?

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

Public exploit code:

- https://github.com/RxRCoder/CVE-2023-2437 (github_poc): https://github.com/RxRCoder/CVE-2023-2437
- UserPro <= 5.1.1 - Authentication Bypass (nuclei): http/cves/2023/CVE-2023-2437.yaml

## Other vulnerabilities in UserPro - Community and User Profile WordPress Plugin

- [CVE-2024-35700](https://insights.sbomify.com/CVE-2024-35700/): WordPress UserPro plugin <= 5.1.8 - Unauthenticated Account Takeover vulnerability (critical 9.8)
- [CVE-2023-2449](https://insights.sbomify.com/CVE-2023-2449/): UserPro <= 5.1.1 - Insecure Password Reset Mechanism (critical 9.8)
- [CVE-2017-16562](https://insights.sbomify.com/CVE-2017-16562/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-2440](https://insights.sbomify.com/CVE-2023-2440/): UserPro <= 5.1.1 - Cross-Site Request Forgery to Privilege Escalation (high 8.8)
- [CVE-2023-2497](https://insights.sbomify.com/CVE-2023-2497/): UserPro <= 5.1.0 - Cross-Site Request Forgery to PHP Object Injection (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2437 and fix it if it is affected.

What it is: CVE-2023-2437 is a critical authentication bypass vulnerability in UserPro - Community and User Profile WordPress Plugin, published on 22 Nov 2023. 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-2023-2437 exists.

Affected product: UserPro - Community and User Profile WordPress 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-2023-2437/ (Markdown: https://insights.sbomify.com/CVE-2023-2437/index.md)
```

## Sources

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

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