WPC Product Options for WooCommerce < 3.1.3 - Authenticated (Subscriber+) Local File Inclusion
Strategic Overview
- Status
- Patched in 3.1.3
- Affected Plugin
- WPC Product Options for WooCommerce
- Affected Version
< 3.1.3- CVSS
- 7.5High
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2025-60248
At a glance
CVE-2025-60248 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the WPC Product Options for WooCommerce WordPress plugin, affecting versions < 3.1.3. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.1.3; sites on affected versions should update now. Disclosed May 2025, reported by Martino Spagnuolo.
Vulnerability Overview
The WPC Product Options for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and excluding, 3.1.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other "safe" file types can be uploaded and included.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
WPC Product Options for WooCommerce < 3.1.3 carries this weakness at safe, and reaching it takes an account at Subscriber level or above. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.
Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For WPC Product Options for WooCommerce the fix is 3.1.3: builds < 3.1.3 are affected, anything from 3.1.3 onward is not.
Remediation
Update to version 3.1.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WPC Product Options for WooCommerce 3.1.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in WPC Product Options for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C