# CVE-2025-32137: WordPress s2Member plugin <= 250419 - Local File Inclusion vulnerability

> An attacker can exploit a relative path traversal flaw in the s2Member WordPress plugin to read arbitrary files from the server.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-292w-2m2h-rw25

## What is CVE-2025-32137?

CVE-2025-32137 is a medium-severity path traversal vulnerability in Cristián Lávaque s2Member, published on 4 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Relative Path Traversal vulnerability in Cristián Lávaque s2Member s2member allows Path Traversal.This issue affects s2Member: from n/a through <= 250419.

Weakness: CWE-23 (Relative Path Traversal)

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


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

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

## Is CVE-2025-32137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32137 is a medium-severity path traversal vulnerability in Cristián Lávaque s2Member, published on 4 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32137 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-32137/ (Markdown: https://insights.sbomify.com/CVE-2025-32137/index.md)
```

## Sources

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

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