Approved changes feed: RSS · Atom
cpe:2.3:a:tainacan:tainacan:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Tainacan (9df0ee6d-ed76-5971-9e2a-2e529b1dde73) |
|---|---|
| Product | Tainacan (8a04950f-afd5-5ebe-a136-49245f4d7797) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/tainacan/tainacan |
purl2cpe | 2026-06-01 10:18:06.469253 |
pkg:github/tainacan/tainacan |
purl2cpe | 2026-06-01 10:18:06.469257 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-6230 |
vulnerable | 2026-07-29 01:06:20.568873 |
Tainacan <= 1.0.3 - Unauthenticated SQL Injection via 'geoquery' REST API Parameter
HIGH (7.5)
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 on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Published: 2026-07-08T11:30:32.366Z
Updated: 2026-07-08T14:00:11.719Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42740 |
vulnerable | 2026-06-08 08:03:16.630543 |
WordPress Tainacan plugin <= 1.0.3 - SQL Injection vulnerability
CRITICAL (9.3)
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in tainacan Tainacan tainacan allows Blind SQL Injection.This issue affects Tainacan: from n/a through <= 1.0.3.
Published: 2026-05-27T09:49:05.087Z
Updated: 2026-05-27T10:51:28.571Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-47512 |
vulnerable | 2026-06-08 07:27:14.490228 |
WordPress Tainacan plugin <= 0.21.14 - Arbitrary File Deletion vulnerability
HIGH (8.6)
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in tainacan Tainacan tainacan allows Path Traversal.This issue affects Tainacan: from n/a through <= 0.21.14.
Published: 2025-05-23T12:43:34.169Z
Updated: 2026-04-28T16:12:43.569Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-14043 |
vulnerable | 2026-06-08 07:06:33.452723 |
Tainacan <= 1.0.1 - Missing Authorization to Unauthenticated Arbitrary Metadata Section Creation
MEDIUM (5.3)
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. This is due to the `create_item_permissions_check()` function unconditionally returning true, which bypasses authentication and authorization validation. This makes it possible for unauthenticated attackers to create arbitrary metadata sections for any collection via the public REST API granted they can access the WordPress site.
Published: 2025-12-21T02:20:32.422Z
Updated: 2026-04-08T16:53:31.704Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-12747 |
vulnerable | 2026-06-08 07:04:30.755348 |
Tainacan <= 1.0.0 - Unauthenticated Information Exposure
MEDIUM (5.3)
The Tainacan plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.0.0 via uploaded files marked as private being exposed in wp-content without adequate protection. This makes it possible for unauthenticated attackers to extract potentially sensitive information from files that have been marked as private.
Published: 2025-11-21T16:28:14.277Z
Updated: 2026-04-08T17:21:09.919Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-12746 |
vulnerable | 2026-06-08 07:04:30.755031 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9221 |
vulnerable | 2026-06-08 07:00:26.950703 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-7135 |
vulnerable | 2026-06-08 06:58:21.342316 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-48040 |
vulnerable | 2026-06-08 06:48:13.577493 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-34795 |
vulnerable | 2026-06-08 06:37:35.033798 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-34794 |
vulnerable | 2026-06-08 06:37:35.031601 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-30529 |
vulnerable | 2026-06-08 06:35:30.523506 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1435 |
vulnerable | 2026-06-08 06:25:40.063133 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-13236 |
vulnerable | 2026-06-08 06:25:37.038418 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.