MultiSafepay plugin for WooCommerce <= 4.15.0 - Arbitrary File Read
Strategic Overview
- Status
- Patched in 4.16.0
- Affected Plugin
- MultiSafepay plugin for WooCommerce
- Affected Version
<= 4.15.0- CVSS
- 7.5High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2022-33901
At a glance
CVE-2022-33901 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the MultiSafepay plugin for WooCommerce WordPress plugin, affecting versions <= 4.15.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.16.0; sites on affected versions should update now. Disclosed July 2022, reported by Brandon James Roldan (tomorrowisnew).
Vulnerability Overview
The MultiSafepay plugin for WooCommerce plugin for WordPress is vulnerable to arbitrary file read in versions up to, and including, 4.15.0 via the log_filename parameter. This is due to insufficient file path validation. This makes it possible for unauthenticated attackers to read arbitrary files on the server, including sensitive configuration files like wp-config.php.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in MultiSafepay plugin for WooCommerce <= 4.15.0 takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For MultiSafepay plugin for WooCommerce the fix is 4.16.0: builds <= 4.15.0 are affected, anything from 4.16.0 onward is not.
Remediation
Update to version 4.16.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to MultiSafepay plugin for WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MultiSafepay plugin for WooCommerce 4.16.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C