CVE-2026-104743: Tainacan advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

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.

Description quoted from the CVE record (assigned by Wordfence, published 2026-10-28).

Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

How it can be exploited

Exploitable over the network with low attack complexity needing high privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS: 0.008
low predicted chance of attack
VEDAS: 0.986
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
Tainacan	up to and including 1.3.0	Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-104743 Tainacan - Importer tmp_file Directory Traversal Attempt. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-104743 Tainacan - Importer tmp_file Directory Traversal Attempt"; flow:established,to_server; http.uri; content:"importers/session/"; nocase; fast_pattern; http.request_body; content:"tmp_file"; nocase; content:".."; distance:0; pcre:"/tmp_file[^\x3b]{0,64}\.\.[\x2f\x5c]/i"; classtype:web-application-attack; reference:cve,CVE-2026-104743; reference:url,https://www.exploit.observer/?keyword=CVE-2026-104743&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=tainacan&match=exact; metadata:created_at 2026_10_29, confidence Medium, signature_severity Major; sid:1089001; rev:1;)

CVE-2026-104743.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.