Tainacan vulnerabilities

The Tainacan plugin for WordPress is vulnerable to time-based blind SQL injection via the 'geoquery' parameter in all versions up to and including 1.0.3 due to insufficient escaping and lack of proper query preparation.

CVE-2026-42740 describes an improper neutralization of special elements used in SQL commands, leading to a Blind SQL Injection vulnerability in the Tainacan system. This issue affects Tainacan versions from n/a through 1.0.3.

The Tainacan plugin for WordPress in versions up to and including 1.3.0 is vulnerable to Directory Traversal via the 'guid' parameter. Authenticated attackers with subscriber-level access and above can read the contents of arbitrary files on the server, which can contain sensitive information.

The Tainacan WordPress plugin before 1.4.0 does not restrict its reports REST endpoints to users with a management capability. This allows any authenticated subscriber to read the email addresses of the repository's staff.

Tainacan through version 1.3.0 contains a deserialization of untrusted data vulnerability that allows Object Injection. An attacker can exploit this to execute malicious code or manipulate application objects.

The Tainacan plugin in versions up to and including 1.2.0 contains an SQL Injection vulnerability accessible to users with the Subscriber role. This allows injection of SQL code into database queries.

The Tainacan plugin for WordPress is vulnerable to unauthorized metadata section creation due to missing authorization checks in all versions up to, and including, 1.0.1. The create_item_permissions_check() function unconditionally returns true, bypassing authentication and authorization validation.

The Tainacan plugin for WordPress in all versions up to and including 1.0.0 is vulnerable to Information Exposure via uploaded files marked as private being exposed in wp-content without adequate protection. This allows unauthenticated attackers to extract potentially sensitive information from files marked as private.

The Tainacan plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'search' parameter in all versions up to, and including, 1.0.0 due to insufficient input sanitization and output escaping.