# CVE-2025-12835: WooMulti <= 1.7 - Subscriber+ Arbitrary File Deletion

> Authenticated users can delete arbitrary files on the server due to lack of validation in the WooMulti WordPress plugin.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Dec 2025
- **Updated:** 12 Dec 2025
- **Also known as:** GHSA-7m2h-m3fc-4qj7

## What is CVE-2025-12835?

CVE-2025-12835 is a high-severity path traversal vulnerability in Unknown WooMulti, published on 12 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The WooMulti WordPress plugin through 17 does not validate a file parameter when deleting files, which could allow any authenticated users, such as subscriber to delete arbitrary files on the server.

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


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

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

## Is CVE-2025-12835 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12835 is a high-severity path traversal vulnerability in Unknown WooMulti, published on 12 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-12835 in the wild and no public exploit code.

Affected product: Unknown WooMulti. 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-12835/ (Markdown: https://insights.sbomify.com/CVE-2025-12835/index.md)
```

## Sources

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

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