Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-57925: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in immonex immonex Kickstart Team

0
High
VulnerabilityCVE-2025-57925cvecve-2025-57925cwe-98
Published: Mon Sep 22 2025 (09/22/2025, 18:25:09 UTC)
Source: CVE Database V5
Vendor/Project: immonex
Product: immonex Kickstart Team

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in immonex immonex Kickstart Team allows PHP Local File Inclusion. This issue affects immonex Kickstart Team: from n/a through 1.6.9.

AI-Powered Analysis

AILast updated: 09/30/2025, 00:45:43 UTC

Technical Analysis

CVE-2025-57925 is a high-severity vulnerability classified under CWE-98, which pertains to improper control of filenames used in include or require statements within PHP programs. Specifically, this vulnerability affects the immonex Kickstart Team software up to version 1.6.9. The flaw allows for PHP Local File Inclusion (LFI), which means an attacker can manipulate the filename parameter in such a way that arbitrary files on the server can be included and executed within the PHP context. This can lead to remote code execution, data disclosure, and full compromise of the affected system. The vulnerability arises because the application does not properly sanitize or validate user input that controls the file path in include/require statements. The CVSS v3.1 base score is 7.5, indicating a high severity, with the vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. This means the attack can be performed remotely over the network, requires low privileges but no user interaction, and has a high impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the nature of the vulnerability makes it a critical concern for organizations using this software. The lack of available patches at the time of publication increases the urgency for mitigation and monitoring.

Potential Impact

For European organizations using immonex Kickstart Team software, this vulnerability poses a significant risk. Successful exploitation can lead to unauthorized disclosure of sensitive data, including configuration files, credentials, and personal information, potentially violating GDPR and other data protection regulations. The ability to execute arbitrary code on affected servers can result in service disruption, data manipulation, or use of compromised systems as a foothold for lateral movement within corporate networks. This can impact business continuity, damage reputation, and lead to regulatory penalties. Given the high confidentiality, integrity, and availability impacts, organizations in sectors such as finance, healthcare, and critical infrastructure are particularly vulnerable. The remote attack vector and lack of required user interaction mean that attackers can exploit this vulnerability without direct user involvement, increasing the risk of automated or widespread attacks once exploit code becomes available.

Mitigation Recommendations

1. Immediate mitigation should include restricting access to the affected immonex Kickstart Team application to trusted internal networks or VPNs to reduce exposure to external attackers. 2. Implement strict input validation and sanitization on all parameters controlling file inclusion paths, employing whitelisting of allowed filenames or directories. 3. Use PHP configuration directives such as open_basedir to limit the directories accessible by PHP scripts, preventing inclusion of arbitrary files outside designated paths. 4. Monitor web server and application logs for suspicious requests attempting to manipulate include parameters or access unexpected files. 5. Deploy Web Application Firewalls (WAFs) with rules targeting LFI attack patterns to block or alert on exploitation attempts. 6. Engage with the vendor or community to obtain patches or updates as soon as they become available and prioritize timely application of these patches. 7. Conduct a thorough security review and code audit of the application to identify and remediate similar insecure coding practices. 8. Educate development and operations teams about secure coding standards related to file inclusion and input handling to prevent recurrence.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-08-22T11:36:24.369Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68d194c5a6a0abbafb7a3926

Added to database: 9/22/2025, 6:26:13 PM

Last enriched: 9/30/2025, 12:45:43 AM

Last updated: 10/7/2025, 1:51:46 PM

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 are available only with a Pro account. Contact root@offseq.com for access.

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

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats