# CVE-2023-3343: User Registration <= 3.0.1 - Authenticated (Subscriber+) PHP Object Injection

> Authenticated attackers can exploit PHP object injection in the User Registration plugin to potentially execute code or access data if a POP chain exists.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Jul 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-6rv8-qjf4-hjgv

## What is CVE-2023-3343?

CVE-2023-3343 is a high-severity unsafe deserialization vulnerability in wpeverest User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The User Registration plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 3.0.1 via deserialization of untrusted input from the 'profile-pic-url' parameter. This allows authenticated attackers, with subscriber-level permissions and above, to inject a PHP Object. No POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Wpeverest User Registration.

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

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

## Is CVE-2023-3343 being exploited?

There is no known exploitation of CVE-2023-3343 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-2023-3342](https://insights.sbomify.com/CVE-2023-3342/): User Registration <= 3.0.2 - Authenticated (Subscriber+) Arbitrary File Upload (critical 9.9)
- [CVE-2022-3912](https://insights.sbomify.com/CVE-2022-3912/): User Registration < 2.2.4.1 - Subscriber+ Arbitrary File Upload (high 7.5)
- [CVE-2025-1511](https://insights.sbomify.com/CVE-2025-1511/): Cross-site scripting in User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder (medium 6.1)
- [CVE-2023-23987](https://insights.sbomify.com/CVE-2023-23987/): WordPress User Registration Plugin <= 2.3.0 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2021-24654](https://insights.sbomify.com/CVE-2021-24654/): User Registration < 2.0.2 - Low Privilege Stored Cross-Site Scripting (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3343 is a high-severity unsafe deserialization vulnerability in wpeverest User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3343 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-2023-3343/ (Markdown: https://insights.sbomify.com/CVE-2023-3343/index.md)
```

## Sources

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

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