Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-32654: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Stylemix Motors

0
Unknown
VulnerabilityCVE-2025-32654cvecve-2025-32654
Published: Fri Apr 11 2025 (04/11/2025, 08:43:01 UTC)
Source: CVE Database V5
Vendor/Project: Stylemix
Product: Motors

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Stylemix Motors motors-car-dealership-classified-listings allows PHP Local File Inclusion.This issue affects Motors: from n/a through <= 1.4.71.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 03:44:55 UTC

Technical Analysis

CVE-2025-32654 is a Local File Inclusion (LFI) vulnerability found in the Stylemix Motors WordPress theme, specifically in the motors-car-dealership-classified-listings component. The vulnerability arises from improper validation or control of filenames passed to PHP include or require statements, which are used to dynamically load files. An attacker can exploit this flaw by manipulating the filename parameter to include arbitrary local files from the server. This can lead to disclosure of sensitive files such as configuration files, password files, or application source code, and in some cases, it may allow remote code execution if the attacker can upload malicious files or leverage other vulnerabilities. The affected versions include all versions up to and including 1.4.71, with no fixed version currently specified. The vulnerability was reserved and published in April 2025, with no CVSS score assigned yet and no known exploits reported in the wild. The issue is critical because it affects a widely used WordPress theme in the automotive dealership sector, which often handles sensitive customer and business data. The lack of authentication requirement lowers the barrier for exploitation, increasing risk. The vulnerability is categorized under improper control of filename for include/require statements, a common PHP security issue that can lead to severe consequences if exploited.

Potential Impact

The impact of CVE-2025-32654 on organizations worldwide can be significant. Exploitation of this LFI vulnerability can lead to unauthorized disclosure of sensitive information such as database credentials, configuration files, or personally identifiable information (PII) stored on the server. This can facilitate further attacks including privilege escalation, remote code execution, or full system compromise. For businesses using the Stylemix Motors theme, particularly automotive dealerships, this could result in data breaches, reputational damage, financial losses, and regulatory penalties. The vulnerability's ease of exploitation without authentication makes it a high-risk threat, especially for websites exposed to the internet. Additionally, attackers could use this vulnerability as a foothold to pivot into internal networks or deploy malware. The absence of known exploits in the wild currently provides a window for proactive mitigation, but the risk remains high due to the common nature of LFI vulnerabilities and the popularity of WordPress themes in general.

Mitigation Recommendations

To mitigate CVE-2025-32654, organizations should first check for updates from Stylemix and apply any available patches that address this vulnerability. If no official patch is available, manual remediation should be undertaken by reviewing and sanitizing all inputs that control file inclusion in the affected PHP scripts. Specifically, developers should implement strict whitelisting of allowed filenames, avoid using user input directly in include/require statements, and employ PHP functions such as realpath() to validate file paths. Disabling remote file inclusion in PHP configuration (allow_url_include=Off) and restricting file permissions to prevent unauthorized file access can also reduce risk. Web application firewalls (WAFs) can be configured to detect and block suspicious requests attempting to exploit LFI. Regular security audits and monitoring for unusual file access patterns are recommended. Finally, organizations should educate developers and administrators about secure coding practices related to file inclusion to prevent similar vulnerabilities in the future.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-04-09T11:21:04.031Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd73eae6bfc5ba1def4085

Added to database: 4/1/2026, 7:37:14 PM

Last enriched: 4/2/2026, 3:44:55 AM

Last updated: 4/6/2026, 11:30:47 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses