# CVE-2026-104743: The Tainacan plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.3.0 via the 'tmp_file' parameter parameter.


- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hjqg-w7m7-3cch

## What is CVE-2026-104743?

CVE-2026-104743 is a medium-severity vulnerability in Tainacan, published on 28 Oct 2026. 

### Official description

The Tainacan plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.3.0 via the 'tmp_file' parameter parameter. This makes it possible for authenticated attackers, with editor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. The poisoned importer path is persisted to the database and later triggered via a separate GET request to the /source_info endpoint, which passes the attacker-controlled path to fopen() and fgetcsv() and returns parsed file contents in the REST response.

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

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


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

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

## Is CVE-2026-104743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104743 is a medium-severity vulnerability in Tainacan, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-104743 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-104743/ (Markdown: https://insights.sbomify.com/CVE-2026-104743/index.md)
```

## Sources

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

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