# CVE-2026-77693: Order Tip for WooCommerce < 1.6.0 - Shop Manager+ Arbitrary File Deletion via delete_exported_csv_file_ajax

> Shop Managers can delete arbitrary files via path traversal, potentially leading to site takeover.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-6vg6-hvwg-vvx8

## What is CVE-2026-77693?

CVE-2026-77693 is a high-severity path traversal vulnerability in Unknown Order Tip for WooCommerce, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Order Tip for WooCommerce WordPress plugin before 1.6.0 does not check the capability of the user requesting a file deletion, nor does it restrict which path may be deleted, allowing users with the Shop Manager role and above to delete arbitrary files on the server, which could lead to the site being taken over.

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

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


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

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

## Is CVE-2026-77693 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77693 is a high-severity path traversal vulnerability in Unknown Order Tip for WooCommerce, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77693 in the wild and no public exploit code.

Affected product: Unknown Order Tip for WooCommerce. 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-77693/ (Markdown: https://insights.sbomify.com/CVE-2026-77693/index.md)
```

## Sources

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

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