# CVE-2026-93767: Tainacan <= 1.3.0 - Authenticated (Subscriber+) Path Traversal to Arbitrary File Read via 'guid' Parameter

> Authenticated attackers can read arbitrary server files via path traversal in the Tainacan WordPress plugin when a specific directory is missing.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-9q7f-9qf7-62pg

## What is CVE-2026-93767?

CVE-2026-93767 is a medium-severity path traversal vulnerability in Tainacan, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Tainacan plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.3.0 via the 'guid' parameter parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. This vulnerability is exploitable only when the uploads/tainacan directory does not exist on the server, as this condition causes realpath() to return false, collapsing the base path to an empty string and rendering the containment check ineffective.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-93767 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93767 is a medium-severity path traversal vulnerability in Tainacan, published on 16 Oct 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-93767 in the wild and no public exploit code.

Affected product: Tainacan. 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-93767/ (Markdown: https://insights.sbomify.com/CVE-2026-93767/index.md)
```

## Sources

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

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