VanKarWai Airtifact Plugin up to 1.2.91 on WordPress filename control

Summaryinfo

A vulnerability was found in VanKarWai Airtifact Plugin up to 1.2.91 on WordPress. It has been rated as critical. This affects an unknown part. The manipulation leads to filename control. This vulnerability is uniquely identified as CVE-2026-27343. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, has been found in VanKarWai Airtifact Plugin up to 1.2.91 on WordPress. This issue affects an unknown function. The manipulation with an unknown input leads to a filename control vulnerability. Using CWE to declare the problem leads to CWE-98. The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in VanKarWai Airtifact airtifact allows PHP Local File Inclusion.This issue affects Airtifact: from n/a through <= 1.2.91.

The weakness was disclosed by João Pedro S Alcântara. The advisory is shared at patchstack.com. The identification of this vulnerability is CVE-2026-27343 since 02/19/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/22/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• VanKarWai

Name

• Airtifact Plugin

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5
• 1.2.6
• 1.2.7
• 1.2.8
• 1.2.9
• 1.2.10
• 1.2.11
• 1.2.12
• 1.2.13
• 1.2.14
• 1.2.15
• 1.2.16
• 1.2.17
• 1.2.18
• 1.2.19
• 1.2.20
• 1.2.21
• 1.2.22
• 1.2.23
• 1.2.24
• 1.2.25
• 1.2.26
• 1.2.27
• 1.2.28
• 1.2.29
• 1.2.30
• 1.2.31
• 1.2.32
• 1.2.33
• 1.2.34
• 1.2.35
• 1.2.36
• 1.2.37
• 1.2.38
• 1.2.39
• 1.2.40
• 1.2.41
• 1.2.42
• 1.2.43
• 1.2.44
• 1.2.45
• 1.2.46
• 1.2.47
• 1.2.48
• 1.2.49
• 1.2.50
• 1.2.51
• 1.2.52
• 1.2.53
• 1.2.54
• 1.2.55
• 1.2.56
• 1.2.57
• 1.2.58
• 1.2.59
• 1.2.60
• 1.2.61
• 1.2.62
• 1.2.63
• 1.2.64
• 1.2.65
• 1.2.66
• 1.2.67
• 1.2.68
• 1.2.69
• 1.2.70
• 1.2.71
• 1.2.72
• 1.2.73
• 1.2.74
• 1.2.75
• 1.2.76
• 1.2.77
• 1.2.78
• 1.2.79
• 1.2.80
• 1.2.81
• 1.2.82
• 1.2.83
• 1.2.84
• 1.2.85
• 1.2.86
• 1.2.87
• 1.2.88
• 1.2.89
• 1.2.90
• 1.2.91

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion