CVE-2024-7135

Tainacan <= 0.21.7 - Missing Authorization to Authenticated (Subscriber+) Arbitrary File Read

2024-07-30 00:00
1337_Wannabe

Strategic Overview

Status
Patched in 0.21.8
Affected Plugin
Tainacan
Affected Version
<= 0.21.7
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-7135
View all Tainacan vulnerabilities

At a glance

CVE-2024-7135 is a medium-severity Missing Authorization vulnerability in the Tainacan WordPress plugin, affecting versions <= 0.21.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.21.8; sites on affected versions should update now. Disclosed July 2024, reported by 1337_Wannabe.

Vulnerability Overview

The Tainacan plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'get_file' function in all versions up to, and including, 0.21.7. The function is also vulnerable to directory traversal. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Tainacan <= 0.21.7 carries this weakness at get_file, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Tainacan the fix is 0.21.8: builds <= 0.21.7 are affected, anything from 0.21.8 onward is not.

Remediation

Update to version 0.21.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Tainacan 0.21.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-7135https://www.wordfence.com/threat-intel/vulnerabilities/id/e4dd0c6a-75af-4b53-ac13-fc4ef0e9001dhttps://nvd.nist.gov/vuln/detail/CVE-2024-7135

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C