# CVE-2026-77005: Code Monkeys Proposals <= 1.0.1 - Subscriber+ Arbitrary File Deletion via Path Traversal

> Authenticated users can delete arbitrary files via path traversal, potentially leading to site takeover.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2026
- **Updated:** 12 Sep 2026
- **Also known as:** GHSA-3mph-m2wr-4wh3

## What is CVE-2026-77005?

CVE-2026-77005 is a critical path traversal vulnerability in Unknown CODE MONKEYS PROPOSALS, published on 12 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The CODE MONKEYS PROPOSALS  WordPress plugin through 1.0.1 does not validate a user-supplied file path before deleting a file, and does not check the capability of the user making the request, allowing any authenticated user, such as a subscriber, to delete arbitrary files on the server, which can lead to a site takeover.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-77005?


## How do I fix CVE-2026-77005?

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

## Is CVE-2026-77005 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77005 and fix it if it is affected.

What it is: CVE-2026-77005 is a critical path traversal vulnerability in Unknown CODE MONKEYS PROPOSALS, published on 12 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77005 in the wild and no public exploit code.

Affected product: Unknown CODE MONKEYS PROPOSALS. 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-2026-77005/ (Markdown: https://insights.sbomify.com/CVE-2026-77005/index.md)
```

## Sources

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

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