# CVE-2023-52200: WordPress ARMember Plugin <= 4.0.22 is vulnerable to Cross Site Request Forgery (CSRF) leading to PHP Object Injection

> Attackers can exploit CSRF to trigger PHP object injection, potentially leading to remote code execution on WordPress sites using the ARMember plugin.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jan 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-gg47-6mxg-9jcv

## What is CVE-2023-52200?

CVE-2023-52200 is a critical unsafe deserialization vulnerability in Repute Infosystems ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF), Deserialization of Untrusted Data vulnerability in Repute Infosystems ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup.This issue affects ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup: n/a.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Reputeinfosystems Armember.

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

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

## Is CVE-2023-52200 being exploited?

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

## Other vulnerabilities in Repute Infosystems ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup

- [CVE-2024-32948](https://insights.sbomify.com/CVE-2024-32948/): WordPress ARMember – Membership Plugin plugin <= 4.0.28 - Broken Access Control vulnerability (critical 9.1)
- [CVE-2024-30223](https://insights.sbomify.com/CVE-2024-30223/): WordPress ARMember plugin <= 4.0.26 - Unauthenticated PHP Object Injection vulnerability (critical 9.0)
- [CVE-2023-51356](https://insights.sbomify.com/CVE-2023-51356/): WordPress ARMember plugin <= 4.0.10 - Privilege Escalation vulnerability (high 8.8)
- [CVE-2024-30222](https://insights.sbomify.com/CVE-2024-30222/): WordPress ARMember plugin <= 4.0.26 - PHP Object Injection vulnerability (high 8.5)
- [CVE-2023-47837](https://insights.sbomify.com/CVE-2023-47837/): WordPress ARMember plugin <= 4.0.10 - Membership Plan Bypass vulnerability (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52200 is a critical unsafe deserialization vulnerability in Repute Infosystems ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-52200 in the wild and no public exploit code.

Affected product: Repute Infosystems ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup. 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-52200/ (Markdown: https://insights.sbomify.com/CVE-2023-52200/index.md)
```

## Sources

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

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