# CVE-2018-25335: WordPress Plugin Peugeot Music 1.0 Arbitrary File Upload

> Unauthenticated attackers can upload malicious files to the Peugeot Music WordPress plugin to execute arbitrary code.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-gvq2-4mf3-84fh

## What is CVE-2018-25335?

CVE-2018-25335 is a critical vulnerability in peugeot-music-plugin Peugeot Music, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Plugin Peugeot Music 1.0 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious files by sending POST requests to the upload.php endpoint. Attackers can upload files with arbitrary extensions by manipulating the 'name' parameter to execute code from the uploads directory.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2018-25335?


## How do I fix CVE-2018-25335?

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

## Is CVE-2018-25335 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25335 and fix it if it is affected.

What it is: CVE-2018-25335 is a critical vulnerability in peugeot-music-plugin Peugeot Music, published on 17 May 2026. 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-2018-25335 in the wild and no public exploit code.

Affected product: peugeot-music-plugin Peugeot Music. 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-2018-25335/ (Markdown: https://insights.sbomify.com/CVE-2018-25335/index.md)
```

## Sources

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

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