# CVE-2025-62023: WordPress s2Member plugin <= 250905 - Remote Code Execution (RCE) vulnerability

> Attackers can execute arbitrary code remotely via a code injection flaw in the s2Member WordPress plugin.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-82m2-w5q8-xfh9

## What is CVE-2025-62023?

CVE-2025-62023 is a critical code injection vulnerability in Cristián Lávaque s2Member, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in Cristián Lávaque s2Member s2member.This issue affects s2Member: from n/a through 250905.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-62023 being exploited?

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

Public exploit code:

- s2Member (WordPress) Unauth RCE via SP Tracking Codes eval() + BONUS: incomplete-fix bypass — IPN notify vector still open in 251005..2512xx   (fixed only in 260101, strip_php_tags_deep added to notify handler //251226). (github_poc): https://github.com/josemour8/CVE-2025-62023

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62023 is a critical code injection vulnerability in Cristián Lávaque s2Member, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62023 in the wild and no public exploit code.

Affected product: Cristián Lávaque s2Member. 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-62023/ (Markdown: https://insights.sbomify.com/CVE-2025-62023/index.md)
```

## Sources

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

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