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-2026-32504: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in CreativeWS VintWood

0
Unknown
VulnerabilityCVE-2026-32504cvecve-2026-32504
Published: Wed Mar 25 2026 (03/25/2026, 16:15:01 UTC)
Source: CVE Database V5
Vendor/Project: CreativeWS
Product: VintWood

Description

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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/25/2026, 17:21:16 UTC

Technical Analysis

CVE-2026-32504 is a Local File Inclusion (LFI) vulnerability found in the CreativeWS VintWood PHP application, affecting versions up to 1.1.8. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to influence which files the application loads. This can lead to unauthorized disclosure of sensitive files on the server, such as configuration files, source code, or credentials. In some cases, LFI can be escalated to Remote Code Execution (RCE) if the attacker can include files containing malicious code or leverage other vulnerabilities. The vulnerability is classified as an improper control of filename for include/require statements, a common PHP security issue. No CVSS score has been assigned yet, and no public exploits have been reported, but the flaw is significant given the widespread use of PHP and the critical role of file inclusion in web applications. The vulnerability was published on March 25, 2026, with no patch links currently available, indicating that users must rely on mitigations or vendor updates once released. The vulnerability affects the confidentiality and integrity of the affected systems, as attackers can read sensitive files or potentially execute arbitrary code. The lack of authentication or user interaction requirements is not explicitly stated but typical LFI vulnerabilities often do not require authentication if the vulnerable endpoint is publicly accessible.

Potential Impact

The impact of CVE-2026-32504 on organizations worldwide can be severe. Exploitation of this LFI vulnerability can lead to unauthorized access to sensitive information such as configuration files, user data, or credentials, compromising confidentiality. In some scenarios, attackers may escalate the attack to execute arbitrary code on the server, threatening system integrity and availability. This could result in full system compromise, data breaches, or service disruptions. Organizations relying on VintWood for web applications may face reputational damage, regulatory penalties, and operational downtime. The risk is heightened for organizations with internet-facing VintWood deployments lacking proper input validation or access controls. Additionally, attackers could use the vulnerability as a foothold for lateral movement within internal networks. Given the absence of known exploits, the threat is currently theoretical but should be treated proactively to prevent future attacks.

Mitigation Recommendations

To mitigate CVE-2026-32504, organizations should implement the following specific measures: 1) Immediately review and restrict the use of include/require statements to fixed, whitelisted file paths, avoiding dynamic input where possible. 2) Implement rigorous input validation and sanitization on all parameters influencing file inclusion to prevent injection of malicious file paths. 3) Employ PHP configuration directives such as open_basedir to limit accessible directories for file operations. 4) Monitor web application logs for suspicious file inclusion attempts or unusual parameter values. 5) If available, apply vendor patches or updates addressing this vulnerability as soon as they are released. 6) Use web application firewalls (WAFs) with rules designed to detect and block LFI attack patterns. 7) Conduct security code reviews and penetration testing focused on file inclusion vulnerabilities. 8) Isolate the vulnerable application environment to limit potential damage from exploitation. 9) Educate developers on secure coding practices related to file inclusion in PHP. These steps go beyond generic advice by focusing on controlling file inclusion paths, proactive monitoring, and environment hardening.

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
2026-03-12T11:12:07.664Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69c4117ef4197a8e3b6d6a41

Added to database: 3/25/2026, 4:46:54 PM

Last enriched: 3/25/2026, 5:21:16 PM

Last updated: 3/26/2026, 5:36:57 AM

Views: 3

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