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-60047: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in axiomthemes IPharm

0
High
VulnerabilityCVE-2025-60047cvecve-2025-60047
Published: Thu Dec 18 2025 (12/18/2025, 07:22:01 UTC)
Source: CVE Database V5
Vendor/Project: axiomthemes
Product: IPharm

Description

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

AI-Powered Analysis

AILast updated: 01/20/2026, 21:29:21 UTC

Technical Analysis

CVE-2025-60047 is a Remote File Inclusion (RFI) vulnerability found in the PHP-based axiomthemes IPharm product, affecting all versions up to and including 1.2.3. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to manipulate the input to include remote or local files. This can lead to arbitrary code execution on the server, as the attacker can inject malicious PHP code via a crafted URL or request parameter. The vulnerability does not require authentication (PR:N) but does require some user interaction (UI:R), such as clicking a malicious link. The CVSS 3.1 score of 8.1 reflects high impact on confidentiality and integrity, with no impact on availability. The scope is unchanged (S:U), meaning the vulnerability affects only the vulnerable component. Although no public exploits are known yet, the nature of RFI vulnerabilities makes them attractive targets for attackers aiming to compromise web servers, steal sensitive data, or pivot within networks. The affected product, IPharm, is used in healthcare-related web applications, increasing the risk due to the sensitivity of the data involved. The vulnerability was reserved in September 2025 and published in December 2025, with no patches currently linked, indicating a potential window of exposure.

Potential Impact

For European organizations, especially those in healthcare and pharmaceutical sectors using the IPharm product, this vulnerability poses a significant risk. Successful exploitation could lead to unauthorized disclosure of sensitive patient data, alteration of critical application logic, and potential breach of regulatory compliance such as GDPR. The ability to execute arbitrary code remotely without authentication could allow attackers to establish persistent access, move laterally within networks, or disrupt services indirectly. Given the critical nature of healthcare data and the increasing targeting of healthcare infrastructure by cybercriminals and nation-state actors, the impact extends beyond individual organizations to national healthcare systems. Additionally, compromised systems could be used as launchpads for further attacks against European supply chains or critical infrastructure. The lack of available patches increases the urgency for immediate mitigation to prevent exploitation.

Mitigation Recommendations

1. Immediately audit all instances of IPharm and identify affected versions (<=1.2.3). 2. If patches become available from axiomthemes, apply them promptly. 3. In the absence of patches, implement strict input validation and sanitization on all parameters that influence file inclusion, ensuring only allowed filenames or paths are accepted. 4. Configure PHP settings to disable remote file inclusion (e.g., setting 'allow_url_include' to 'Off' and 'allow_url_fopen' to 'Off'). 5. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests attempting to exploit file inclusion. 6. Restrict filesystem permissions to limit the web server's ability to read or execute files outside designated directories. 7. Monitor logs for unusual access patterns or errors related to file inclusion attempts. 8. Educate developers and administrators about secure coding practices to prevent similar vulnerabilities. 9. Consider network segmentation to isolate vulnerable systems until fully remediated.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-09-25T15:19:17.077Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6943b0494eb3efac366ffa78

Added to database: 12/18/2025, 7:42:01 AM

Last enriched: 1/20/2026, 9:29:21 PM

Last updated: 2/6/2026, 12:33:52 AM

Views: 29

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats