CVE-2025-60204: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Josh Kohlbach WooCommerce Store Toolkit
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Josh Kohlbach WooCommerce Store Toolkit woocommerce-store-toolkit allows PHP Local File Inclusion.This issue affects WooCommerce Store Toolkit: from n/a through <= 2.4.3.
AI Analysis
Technical Summary
CVE-2025-60204 is a remote file inclusion (RFI) vulnerability found in the Josh Kohlbach WooCommerce Store Toolkit plugin for WordPress, affecting versions up to 2.4.3. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to specify a remote file to be included and executed by the server. This type of vulnerability enables attackers to execute arbitrary PHP code remotely, potentially leading to unauthorized data disclosure or further compromise of the web server. The vulnerability does not require authentication or user interaction and can be exploited remotely over the network, increasing its risk profile. The CVSS v3.1 base score is 7.5, reflecting a high severity due to the network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact primarily affects confidentiality, as attackers can execute code that may expose sensitive information, though integrity and availability are not directly impacted. No known exploits are currently reported in the wild, but the vulnerability's nature makes it a prime target for attackers once publicized. The lack of available patches at the time of disclosure necessitates immediate attention from administrators using this plugin. The vulnerability is particularly critical for e-commerce platforms relying on WooCommerce, as exploitation could lead to customer data exposure or site compromise.
Potential Impact
For European organizations, especially those operating e-commerce platforms using WooCommerce with the vulnerable Store Toolkit plugin, this vulnerability poses a significant risk to customer data confidentiality and overall platform security. Successful exploitation could lead to unauthorized disclosure of sensitive customer information, including personal and payment data, damaging brand reputation and potentially violating GDPR requirements. Although integrity and availability are not directly compromised, the ability to execute arbitrary code remotely could be leveraged for further attacks, such as deploying malware or pivoting within the network. The widespread adoption of WooCommerce across Europe, particularly in countries with mature e-commerce markets like Germany, the UK, France, and the Netherlands, increases the potential attack surface. Additionally, the vulnerability's ease of exploitation without authentication or user interaction makes it a critical concern for organizations lacking robust web application security controls. Failure to address this vulnerability promptly could result in regulatory penalties, financial losses, and erosion of customer trust.
Mitigation Recommendations
1. Immediately identify and inventory all instances of the WooCommerce Store Toolkit plugin in use, focusing on versions up to 2.4.3. 2. Apply any available patches or updates from the vendor as soon as they are released. If no patch is available, consider disabling or uninstalling the vulnerable plugin until a fix is provided. 3. Implement strict input validation and sanitization on all parameters that influence file inclusion to prevent injection of remote file paths. 4. Employ web application firewalls (WAFs) with rules designed to detect and block remote file inclusion attempts, especially those targeting known vulnerable endpoints. 5. Restrict outgoing HTTP requests from the web server to prevent the inclusion of remote files from untrusted sources. 6. Conduct regular security audits and penetration testing focused on plugin vulnerabilities within the e-commerce environment. 7. Monitor logs for suspicious activity indicative of exploitation attempts, such as unusual include requests or unexpected remote connections. 8. Educate development and operations teams about secure coding practices related to file inclusion and plugin management. 9. Ensure backups are current and tested to enable rapid recovery in case of compromise. 10. Coordinate with legal and compliance teams to prepare for potential data breach notifications if exploitation occurs.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Sweden
CVE-2025-60204: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Josh Kohlbach WooCommerce Store Toolkit
Description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Josh Kohlbach WooCommerce Store Toolkit woocommerce-store-toolkit allows PHP Local File Inclusion.This issue affects WooCommerce Store Toolkit: from n/a through <= 2.4.3.
AI-Powered Analysis
Technical Analysis
CVE-2025-60204 is a remote file inclusion (RFI) vulnerability found in the Josh Kohlbach WooCommerce Store Toolkit plugin for WordPress, affecting versions up to 2.4.3. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to specify a remote file to be included and executed by the server. This type of vulnerability enables attackers to execute arbitrary PHP code remotely, potentially leading to unauthorized data disclosure or further compromise of the web server. The vulnerability does not require authentication or user interaction and can be exploited remotely over the network, increasing its risk profile. The CVSS v3.1 base score is 7.5, reflecting a high severity due to the network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact primarily affects confidentiality, as attackers can execute code that may expose sensitive information, though integrity and availability are not directly impacted. No known exploits are currently reported in the wild, but the vulnerability's nature makes it a prime target for attackers once publicized. The lack of available patches at the time of disclosure necessitates immediate attention from administrators using this plugin. The vulnerability is particularly critical for e-commerce platforms relying on WooCommerce, as exploitation could lead to customer data exposure or site compromise.
Potential Impact
For European organizations, especially those operating e-commerce platforms using WooCommerce with the vulnerable Store Toolkit plugin, this vulnerability poses a significant risk to customer data confidentiality and overall platform security. Successful exploitation could lead to unauthorized disclosure of sensitive customer information, including personal and payment data, damaging brand reputation and potentially violating GDPR requirements. Although integrity and availability are not directly compromised, the ability to execute arbitrary code remotely could be leveraged for further attacks, such as deploying malware or pivoting within the network. The widespread adoption of WooCommerce across Europe, particularly in countries with mature e-commerce markets like Germany, the UK, France, and the Netherlands, increases the potential attack surface. Additionally, the vulnerability's ease of exploitation without authentication or user interaction makes it a critical concern for organizations lacking robust web application security controls. Failure to address this vulnerability promptly could result in regulatory penalties, financial losses, and erosion of customer trust.
Mitigation Recommendations
1. Immediately identify and inventory all instances of the WooCommerce Store Toolkit plugin in use, focusing on versions up to 2.4.3. 2. Apply any available patches or updates from the vendor as soon as they are released. If no patch is available, consider disabling or uninstalling the vulnerable plugin until a fix is provided. 3. Implement strict input validation and sanitization on all parameters that influence file inclusion to prevent injection of remote file paths. 4. Employ web application firewalls (WAFs) with rules designed to detect and block remote file inclusion attempts, especially those targeting known vulnerable endpoints. 5. Restrict outgoing HTTP requests from the web server to prevent the inclusion of remote files from untrusted sources. 6. Conduct regular security audits and penetration testing focused on plugin vulnerabilities within the e-commerce environment. 7. Monitor logs for suspicious activity indicative of exploitation attempts, such as unusual include requests or unexpected remote connections. 8. Educate development and operations teams about secure coding practices related to file inclusion and plugin management. 9. Ensure backups are current and tested to enable rapid recovery in case of compromise. 10. Coordinate with legal and compliance teams to prepare for potential data breach notifications if exploitation occurs.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Patchstack
- Date Reserved
- 2025-09-25T15:28:42.280Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 690cc80cca26fb4dd2f595d3
Added to database: 11/6/2025, 4:08:44 PM
Last enriched: 1/20/2026, 9:49:24 PM
Last updated: 2/4/2026, 11:16:54 PM
Views: 26
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-1895: Improper Access Controls in WeKan
MediumCVE-2025-22873: CWE-23: Relative Path Traversal in Go standard library os
UnknownCVE-2026-22038: CWE-532: Insertion of Sensitive Information into Log File in Significant-Gravitas AutoGPT
HighCVE-2026-1894: Improper Authorization in WeKan
MediumCVE-2025-62616: CWE-918: Server-Side Request Forgery (SSRF) in Significant-Gravitas AutoGPT
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.