# CVE-2025-2005: Front-End-Only-Users <= 3.2.32 - Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files via the registration form, potentially leading to remote code execution on the server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 2 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-w6ff-xghx-7936

## What is CVE-2025-2005?

CVE-2025-2005 is a critical vulnerability in rustaurius Front End Users, published on 2 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Front End Users plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the file uploads field of the registration form in all versions up to, and including, 3.2.32. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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

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

It affects 1 product.


Products: Etoilewebdesign Front End Users.

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

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

## Is CVE-2025-2005 being exploited?

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

Public exploit code:

-  WordPress Front End Users Plugin <= 3.2.32 is vulnerable to Arbitrary File Upload  (github_poc): https://github.com/Nxploited/CVE-2025-2005
- WordPress FEUP Arbitrary File Upload Exploit (CVE-2025-2005) (github_poc): https://github.com/mrmtwoj/CVE-2025-2005
- Technical security research and PoC for CVE-2025-2005, an unauthenticated arbitrary file upload vulnerability affecting vulnerable versions of the WordPress Front-End Users plugin. Includes vulnerability analysis, attack surface, request flow, controlled PoC, impact assessment, detection guidance, and remediation notes. (github_poc): https://github.com/h4ckxel/CVE-2025-2005

## Other vulnerabilities in rustaurius Front End Users

- [CVE-2024-7607](https://insights.sbomify.com/CVE-2024-7607/): Front End Users <= 3.2.28 - Authenticated (Contributor+) Time-Based SQL Injection (high 8.8)
- [CVE-2024-13569](https://insights.sbomify.com/CVE-2024-13569/): Front End Users <= 3.2.32 - Reflected XSS (high 7.1)
- [CVE-2023-33322](https://insights.sbomify.com/CVE-2023-33322/): WordPress Front End Users plugin < 3.2.25 - Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2025-26877](https://insights.sbomify.com/CVE-2025-26877/): WordPress Front End Users Plugin <= 3.2.30 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2023-34005](https://insights.sbomify.com/CVE-2023-34005/): WordPress Front End Users Plugin <= 3.2.24 is vulnerable to Cross Site Request Forgery (CSRF) (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2005 is a critical vulnerability in rustaurius Front End Users, published on 2 Apr 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-2005 in the wild and no public exploit code.

Affected product: rustaurius Front End Users. 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-2005/ (Markdown: https://insights.sbomify.com/CVE-2025-2005/index.md)
```

## Sources

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

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