sales@hackhalt.com

Home / Threats / CVE-2025-12747

Tainacan - Information Disclosure (CVE-2025-12747)

CVE-2025-12747

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.

CVE-2025-12747

MEDIUM CVSS 5.3 Published 2025-11-21 Updated 2026-06-17
AI Risk High (80/100) Active Exploit: Likely Published Exploit: Public exploit references found Priority: P2 Urgent
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected Components 1
Reference Links 3
AI Risk Engine High (80/100)
Exploitability High
Active Exploitation Likely
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2025-11-21 CVE published and first recorded in the threat feed.
  2. 2026-06-17 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 218 days ago

AI enriched 218 days ago (2026-04-09 07:13 UTC)

Technical Summary

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.

Potential Impact

Severity is MEDIUM (CVSS 5.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on published exploit references, remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: published exploit references, remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Tainacan PLUGIN · tainacan Affected: <= 1.0.0 Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Tainacan to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Restrict REST API in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Require authentication for REST namespaces that do not need to be public, so the API cannot be used to enumerate content and accounts.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Tainacan, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Tainacan. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update Tainacan to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Restrict REST API in Hack Halt Pro contains this class of attack at the request layer.

What can an attacker actually do?

This is a Information Disclosure flaw. An attacker who exploits it can read data they were never meant to see, which is often the first step in a larger attack.