Tatsu: A security weakness

Tatsu is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 8.1 CVSS · contact@wpscan.com

NVD score 8.1 CVSS 3.1 · nvd@nist.gov

Component: Tatsu
Plugin slug: tatsu
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Apr 25, 2022
Weakness: CWE-306 — Missing Authentication for Critical Function

This CVE was published Apr 25, 2022 and is one of 1 known issue for this plugin.

What to do

Update, patch or deactivate.

Update Tatsu to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Tatsu WordPress plugin before 3.3.12 add_custom_font action can be used without prior authentication to upload a rogue zip file which is uncompressed under the WordPress's upload directory. By adding a PHP shell with a filename starting with a dot ".", this can bypass extension control implemented in the plugin. Moreover, there is a race condition in the zip extraction process which makes the shell file live long enough on the filesystem to be callable by an attacker.

NVD vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

References

Update, patch or deactivate.

Technical description

Primary and upstream sources