CVE-2026-24538: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in omnipressteam Omnipress
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in omnipressteam Omnipress omnipress allows PHP Local File Inclusion.This issue affects Omnipress: from n/a through <= 1.6.6.
AI Analysis
Technical Summary
CVE-2026-24538 is a vulnerability classified as 'Improper Control of Filename for Include/Require Statement in PHP Program,' commonly known as a Local File Inclusion (LFI) flaw, found in the Omnipress product by omnipressteam. The vulnerability affects Omnipress versions up to and including 1.6.6. It arises because the application does not properly validate or sanitize user-supplied input used in PHP include or require statements, allowing an attacker with at least low-level privileges to manipulate the filename parameter. This manipulation enables the attacker to include arbitrary local files on the server, potentially exposing sensitive information such as configuration files, source code, or credentials. The CVSS v3.1 score is 7.6, indicating a high severity with the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L, meaning the attack can be launched remotely over the network with low attack complexity, requires low privileges, no user interaction, and impacts confidentiality highly, with limited integrity and availability impacts. Although no known exploits are currently reported in the wild, the vulnerability presents a significant risk due to the potential for information disclosure and partial system compromise. The vulnerability is particularly dangerous in web-facing environments where Omnipress is deployed, as attackers can leverage it to gain insights into the system or pivot to further attacks.
Potential Impact
For European organizations, exploitation of CVE-2026-24538 could lead to unauthorized disclosure of sensitive data, including internal configuration files, user credentials, or proprietary information, severely impacting confidentiality. This could result in compliance violations under GDPR due to data exposure. The partial integrity impact may allow attackers to influence application behavior or escalate privileges, while availability impact, though limited, could disrupt services. Organizations relying on Omnipress for publishing or content management may face operational disruptions and reputational damage. The risk is heightened for sectors with stringent data protection requirements such as finance, healthcare, and government institutions. Additionally, the vulnerability could be leveraged as a foothold for lateral movement within networks, increasing the overall threat landscape.
Mitigation Recommendations
1. Apply official patches or updates from omnipressteam as soon as they become available to address the vulnerability directly. 2. Until patches are released, implement strict input validation and sanitization on all parameters used in include/require statements to ensure only intended files can be included. 3. Employ web application firewalls (WAF) with rules designed to detect and block attempts to exploit file inclusion vulnerabilities. 4. Restrict PHP include paths using configuration directives such as open_basedir to limit accessible directories. 5. Conduct regular code audits and penetration testing focusing on file inclusion and input validation weaknesses. 6. Monitor logs for unusual file access patterns or errors indicative of exploitation attempts. 7. Limit privileges of web server and application accounts to minimize the impact of successful exploitation. 8. Educate development teams on secure coding practices related to file inclusion and input handling.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Belgium
CVE-2026-24538: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in omnipressteam Omnipress
Description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in omnipressteam Omnipress omnipress allows PHP Local File Inclusion.This issue affects Omnipress: from n/a through <= 1.6.6.
AI-Powered Analysis
Technical Analysis
CVE-2026-24538 is a vulnerability classified as 'Improper Control of Filename for Include/Require Statement in PHP Program,' commonly known as a Local File Inclusion (LFI) flaw, found in the Omnipress product by omnipressteam. The vulnerability affects Omnipress versions up to and including 1.6.6. It arises because the application does not properly validate or sanitize user-supplied input used in PHP include or require statements, allowing an attacker with at least low-level privileges to manipulate the filename parameter. This manipulation enables the attacker to include arbitrary local files on the server, potentially exposing sensitive information such as configuration files, source code, or credentials. The CVSS v3.1 score is 7.6, indicating a high severity with the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L, meaning the attack can be launched remotely over the network with low attack complexity, requires low privileges, no user interaction, and impacts confidentiality highly, with limited integrity and availability impacts. Although no known exploits are currently reported in the wild, the vulnerability presents a significant risk due to the potential for information disclosure and partial system compromise. The vulnerability is particularly dangerous in web-facing environments where Omnipress is deployed, as attackers can leverage it to gain insights into the system or pivot to further attacks.
Potential Impact
For European organizations, exploitation of CVE-2026-24538 could lead to unauthorized disclosure of sensitive data, including internal configuration files, user credentials, or proprietary information, severely impacting confidentiality. This could result in compliance violations under GDPR due to data exposure. The partial integrity impact may allow attackers to influence application behavior or escalate privileges, while availability impact, though limited, could disrupt services. Organizations relying on Omnipress for publishing or content management may face operational disruptions and reputational damage. The risk is heightened for sectors with stringent data protection requirements such as finance, healthcare, and government institutions. Additionally, the vulnerability could be leveraged as a foothold for lateral movement within networks, increasing the overall threat landscape.
Mitigation Recommendations
1. Apply official patches or updates from omnipressteam as soon as they become available to address the vulnerability directly. 2. Until patches are released, implement strict input validation and sanitization on all parameters used in include/require statements to ensure only intended files can be included. 3. Employ web application firewalls (WAF) with rules designed to detect and block attempts to exploit file inclusion vulnerabilities. 4. Restrict PHP include paths using configuration directives such as open_basedir to limit accessible directories. 5. Conduct regular code audits and penetration testing focusing on file inclusion and input validation weaknesses. 6. Monitor logs for unusual file access patterns or errors indicative of exploitation attempts. 7. Limit privileges of web server and application accounts to minimize the impact of successful exploitation. 8. Educate development teams on secure coding practices related to file inclusion and input handling.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Patchstack
- Date Reserved
- 2026-01-23T12:31:40.820Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 69738ad94623b1157c48ba2f
Added to database: 1/23/2026, 2:51:05 PM
Last enriched: 1/31/2026, 8:42:04 AM
Last updated: 2/7/2026, 12:57:03 AM
Views: 24
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25762: CWE-400: Uncontrolled Resource Consumption in adonisjs core
HighCVE-2026-25754: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in adonisjs core
HighCVE-2026-25644: CWE-295: Improper Certificate Validation in datahub-project datahub
HighCVE-2026-25804: CWE-287: Improper Authentication in antrea-io antrea
HighCVE-2026-25803: CWE-798: Use of Hard-coded Credentials in denpiligrim 3dp-manager
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.