Read the docs

Path traversal in Tainacan WordPress plugin lets editors read files

Priority LOW 24CWE-22Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-22 and the CVSS impact.

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. An authenticated attacker with editor-level access or above can read the contents of arbitrary files on the server, which may contain sensitive information. The poisoned importer path is stored in the database and then triggered by a separate GET request to the /source_info endpoint, which returns parsed file contents in the REST response.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00841 58th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
tainacanTainacanup to 1.3.0—No fix listedCNA
  • Tainacan Vendortainacan Affected up to 1.3.0 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:tainacan:tainacan:*:*:*:*:*:*:*:*——tainacan
  • cpe:2.3:a:tainacan:tainacan:*:*:*:*:*:*:*:* Versions — — ·tainacan

Remediation

The sources list no fixed version for Tainacan.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-28 Threatist record created from CVE-2026-104743
  2. 2026-10-28 Alias added: GHSA-hjqg-w7m7-3cch
  3. 2026-10-29 CISA SSVC decision points changed

References

  • TI-2024-20253 WordPress Tainacan plugin <= 0.20.7 - Broken Access Control vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2026-30963 WordPress Tainacan plugin <= 1.0.3 - SQL Injection vulnerability CVSS 3.1CRITICAL 9.3
  • TI-2025-30009 WordPress Tainacan plugin <= 0.21.14 - Arbitrary File Deletion vulnerability CVSS 3.1HIGH 8.6
  • TI-2026-05467 Tainacan <= 1.0.3 - Unauthenticated SQL Injection via 'geoquery' REST API Parameter CVSS 3.1HIGH 7.5
  • TI-2024-32242 WordPress Tainacan plugin <= 0.21.8 - SQL Injection vulnerability CVSS 3.1HIGH 8.5
  • TI-2024-06604 Tainacan <= 0.21.7 - Missing Authorization to Authenticated (Subscriber+) Arbitrary File Read CVSS 3.1MEDIUM 6.5
See all 19 →

Sources