Stylemix Motors Plugin up to 1.4.65 on WordPress filename control

Summaryinfo

A vulnerability was found in Stylemix Motors Plugin up to 1.4.65 on WordPress. It has been classified as problematic. This affects an unknown function. This manipulation causes filename control. This vulnerability is tracked as CVE-2025-32654. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Stylemix Motors Plugin up to 1.4.65 on WordPress. It has been declared as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a filename control vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect 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 Stylemix Motors allows PHP Local File Inclusion. This issue affects Motors: from n/a through 1.4.65.

The weakness was disclosed by Lvt-tholv2k. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2025-32654 since 04/09/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 04/11/2025).

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

• Stylemix

Name

• Motors Plugin

Version

• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.4.5
• 1.4.6
• 1.4.7
• 1.4.8
• 1.4.9
• 1.4.10
• 1.4.11
• 1.4.12
• 1.4.13
• 1.4.14
• 1.4.15
• 1.4.16
• 1.4.17
• 1.4.18
• 1.4.19
• 1.4.20
• 1.4.21
• 1.4.22
• 1.4.23
• 1.4.24
• 1.4.25
• 1.4.26
• 1.4.27
• 1.4.28
• 1.4.29
• 1.4.30
• 1.4.31
• 1.4.32
• 1.4.33
• 1.4.34
• 1.4.35
• 1.4.36
• 1.4.37
• 1.4.38
• 1.4.39
• 1.4.40
• 1.4.41
• 1.4.42
• 1.4.43
• 1.4.44
• 1.4.45
• 1.4.46
• 1.4.47
• 1.4.48
• 1.4.49
• 1.4.50
• 1.4.51
• 1.4.52
• 1.4.53
• 1.4.54
• 1.4.55
• 1.4.56
• 1.4.57
• 1.4.58
• 1.4.59
• 1.4.60
• 1.4.61
• 1.4.62
• 1.4.63
• 1.4.64
• 1.4.65

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