CVE-2026-104743 json
Tainacan <= 1.3.0 - Authenticated (Editor+) Path Traversal to Arbitrary File Read via 'tmp_file' Parameter via Mass Assignment
published 12d ago modified 12d ago also EUVD-2026-111612
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-104743 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12d ago
Exploit prediction
0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected products
- tainacan Tainacan
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
- github.com /tainacan/tainacan/commit/1cc2c179d213670ae4bd378473d6fecbc35c6357
- wordfence.com /threat-intel/vulnerabilities/id/e16bda6d-0818-468b-9114-82a8f5f68caf?source=cve
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/api/endpoints/class-tainacan-rest-importers-controller.php#L223
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/background-process/importer/class-tainacan-importer.php#L255
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/background-process/importer/class-tainacan-csv.php#L36
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/background-process/importer/class-tainacan-csv.php#L334
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/background-process/importer/class-tainacan-csv.php#L93
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/api/endpoints/class-tainacan-rest-importers-controller.php#L190
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/api/endpoints/class-tainacan-rest-importers-controller.php#L266
- plugins.trac.wordpress.org /browser/tainacan/tags/1.3.0/classes/api/endpoints/class-tainacan-rest-importers-controller.php#L146
- plugins.trac.wordpress.org /browser/tainacan/tags/1.4.0/classes/api/endpoints/class-tainacan-rest-importers-controller.php
Sources
- CVE List CVE-2026-104743
- NVD CVE-2026-104743
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.