Skip to main content
CVE-2026-104743VulnerabilityPublished

The Tainacan plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.3.0 via

Source GCVE Database

0
Authoritative record:CVE-2026-104743· Medium 4.9

Not known to be exploited · CVSS 4.9 Medium.

Data as of 28 Oct 2026, 10:42 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
tainacanTainacanAffected
  • <=1.3.0
Fixed in–

AI-suggested

Until a fix is available, restrict editor-level access to trusted users only and monitor for updates from the plugin vendor. Avoid exposing the /source_info endpoint unnecessarily.

Description

The Tainacan WordPress plugin versions up to and including 1.3.0 contain a directory traversal vulnerability via the 'tmp_file' parameter. Authenticated users with editor-level or higher privileges can exploit this flaw to read arbitrary files on the server. The vulnerability arises because a manipulated importer path is stored in the database and later accessed through a GET request to the /source_info endpoint, which reads and returns file contents via fopen() and fgetcsv().

References

Community reviews

Loading reviews…