CVE-2025-12968: CWE-434 Unrestricted Upload of File with Dangerous Type in infility Infility Global
The Infility Global plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation and capability checks in all versions up to, and including, 2.14.23. This is due to the `upload_file` function in the `infility_import_file` class only validating the MIME type which can be easily spoofed, and the `import_data` function missing capability checks. This makes it possible for authenticated attackers, with subscriber level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
AI Analysis
Technical Summary
CVE-2025-12968 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) affecting all versions up to 2.14.23 of the Infility Global plugin for WordPress. The root cause is inadequate validation of uploaded files: the plugin's `upload_file` function relies solely on MIME type checks, which attackers can easily spoof to bypass restrictions. Additionally, the `import_data` function lacks proper capability checks, allowing users with subscriber-level access or higher to upload arbitrary files to the server. This combination enables an authenticated attacker to place malicious files on the server, potentially leading to remote code execution (RCE). The vulnerability is remotely exploitable over the network without user interaction, requiring only low-level authenticated access. The CVSS v3.1 base score is 8.8, indicating a high-severity issue with network attack vector, low attack complexity, and high impact on confidentiality, integrity, and availability. No patches or known exploits are currently reported, but the risk remains significant due to the ease of exploitation and potential for full system compromise. The vulnerability affects all versions of the plugin, making it critical for administrators to assess their exposure and implement mitigations promptly.
Potential Impact
For European organizations, this vulnerability poses a significant risk, especially for those relying on WordPress sites with the Infility Global plugin installed. Successful exploitation could lead to unauthorized remote code execution, allowing attackers to execute arbitrary commands, steal sensitive data, deface websites, or disrupt services. This impacts confidentiality, integrity, and availability of affected systems. Organizations in sectors such as finance, healthcare, government, and e-commerce are particularly vulnerable due to the sensitive nature of their data and the criticality of their web infrastructure. The ease of exploitation by low-privilege authenticated users increases the threat surface, as even compromised or low-level accounts could be leveraged for attacks. Given the widespread use of WordPress across Europe and the plugin's presence, the vulnerability could facilitate lateral movement within networks, data breaches, and service outages, potentially leading to regulatory penalties under GDPR for data loss or unauthorized access.
Mitigation Recommendations
1. Immediately restrict file upload permissions to trusted roles only, ideally disabling uploads for subscriber-level users until a patch is available. 2. Implement server-side validation of uploaded files beyond MIME type checks, including verifying file extensions, scanning file contents for malicious code, and enforcing strict whitelist policies. 3. Monitor web server logs and WordPress activity logs for unusual file upload patterns or unauthorized access attempts. 4. Use Web Application Firewalls (WAF) to detect and block suspicious file upload attempts targeting the Infility Global plugin endpoints. 5. Isolate WordPress installations in segmented network zones to limit the impact of potential compromises. 6. Regularly update WordPress plugins and core software; apply security patches from the vendor as soon as they are released. 7. Conduct security awareness training for administrators and users about the risks of low-privilege account compromise and file upload vulnerabilities. 8. Consider deploying runtime application self-protection (RASP) tools to detect and prevent exploitation attempts in real time.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden
CVE-2025-12968: CWE-434 Unrestricted Upload of File with Dangerous Type in infility Infility Global
Description
The Infility Global plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation and capability checks in all versions up to, and including, 2.14.23. This is due to the `upload_file` function in the `infility_import_file` class only validating the MIME type which can be easily spoofed, and the `import_data` function missing capability checks. This makes it possible for authenticated attackers, with subscriber level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
AI-Powered Analysis
Technical Analysis
CVE-2025-12968 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) affecting all versions up to 2.14.23 of the Infility Global plugin for WordPress. The root cause is inadequate validation of uploaded files: the plugin's `upload_file` function relies solely on MIME type checks, which attackers can easily spoof to bypass restrictions. Additionally, the `import_data` function lacks proper capability checks, allowing users with subscriber-level access or higher to upload arbitrary files to the server. This combination enables an authenticated attacker to place malicious files on the server, potentially leading to remote code execution (RCE). The vulnerability is remotely exploitable over the network without user interaction, requiring only low-level authenticated access. The CVSS v3.1 base score is 8.8, indicating a high-severity issue with network attack vector, low attack complexity, and high impact on confidentiality, integrity, and availability. No patches or known exploits are currently reported, but the risk remains significant due to the ease of exploitation and potential for full system compromise. The vulnerability affects all versions of the plugin, making it critical for administrators to assess their exposure and implement mitigations promptly.
Potential Impact
For European organizations, this vulnerability poses a significant risk, especially for those relying on WordPress sites with the Infility Global plugin installed. Successful exploitation could lead to unauthorized remote code execution, allowing attackers to execute arbitrary commands, steal sensitive data, deface websites, or disrupt services. This impacts confidentiality, integrity, and availability of affected systems. Organizations in sectors such as finance, healthcare, government, and e-commerce are particularly vulnerable due to the sensitive nature of their data and the criticality of their web infrastructure. The ease of exploitation by low-privilege authenticated users increases the threat surface, as even compromised or low-level accounts could be leveraged for attacks. Given the widespread use of WordPress across Europe and the plugin's presence, the vulnerability could facilitate lateral movement within networks, data breaches, and service outages, potentially leading to regulatory penalties under GDPR for data loss or unauthorized access.
Mitigation Recommendations
1. Immediately restrict file upload permissions to trusted roles only, ideally disabling uploads for subscriber-level users until a patch is available. 2. Implement server-side validation of uploaded files beyond MIME type checks, including verifying file extensions, scanning file contents for malicious code, and enforcing strict whitelist policies. 3. Monitor web server logs and WordPress activity logs for unusual file upload patterns or unauthorized access attempts. 4. Use Web Application Firewalls (WAF) to detect and block suspicious file upload attempts targeting the Infility Global plugin endpoints. 5. Isolate WordPress installations in segmented network zones to limit the impact of potential compromises. 6. Regularly update WordPress plugins and core software; apply security patches from the vendor as soon as they are released. 7. Conduct security awareness training for administrators and users about the risks of low-privilege account compromise and file upload vulnerabilities. 8. Consider deploying runtime application self-protection (RASP) tools to detect and prevent exploitation attempts in real time.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-10T17:45:07.108Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 693b9182650da22753edbaf3
Added to database: 12/12/2025, 3:52:34 AM
Last enriched: 12/12/2025, 4:01:32 AM
Last updated: 12/14/2025, 6:01:14 PM
Views: 15
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-2025-14673: Heap-based Buffer Overflow in gmg137 snap7-rs
MediumCVE-2025-14668: SQL Injection in campcodes Advanced Online Examination System
MediumCVE-2025-14667: SQL Injection in itsourcecode COVID Tracking System
MediumCVE-2025-14666: SQL Injection in itsourcecode COVID Tracking System
MediumCVE-2025-14665: Stack-based Buffer Overflow in Tenda WH450
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.