Squeeze <= 1.7.7 - Authenticated (Subscriber+) Directory Traversal
Strategic Overview
- Status
- Patched in 1.7.8
- Affected Plugin
- Squeeze – Image Optimization & Compression, WEBP Conversion
- Affected Version
<= 1.7.7- CVSS
- 4.3Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-32415
At a glance
CVE-2026-32415 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Squeeze WordPress plugin, affecting versions <= 1.7.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.7.8; sites on affected versions should update now. Disclosed February 2026, reported by Nabil Irawan.
Vulnerability Overview
The Squeeze – Image Optimization & Compression, WEBP Conversion plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.7.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform actions on files outside of the originally intended directory.
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 interaction from a victim user.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Squeeze <= 1.7.7 takes an account at Subscriber level or above. 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 Squeeze the fix is 1.7.8: builds <= 1.7.7 are affected, anything from 1.7.8 onward is not.
Remediation
Update to version 1.7.8, 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. None of that substitutes for the fix: Squeeze 1.7.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Squeeze – Image Optimization & Compression, WEBP Conversion
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C