# CVE-2025-52758: WordPress Zippy plugin <= 1.7.0 - Arbitrary File Upload vulnerability

> Attackers can upload malicious files to the Zippy WordPress plugin, potentially leading to remote code execution on the server.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-q8gx-mpxq-xjjv

## What is CVE-2025-52758?

CVE-2025-52758 is a critical vulnerability in Gesundheit Bewegt GmbH Zippy, published on 22 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in Gesundheit Bewegt GmbH Zippy zippy allows Using Malicious Files.This issue affects Zippy: from n/a through <= 1.7.0.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-52758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52758 is a critical vulnerability in Gesundheit Bewegt GmbH Zippy, published on 22 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52758 in the wild and no public exploit code.

Affected product: Gesundheit Bewegt GmbH Zippy. 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-52758/ (Markdown: https://insights.sbomify.com/CVE-2025-52758/index.md)
```

## Sources

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

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