CVE-2025-31003

Squeeze <= 1.6 - Authenticated (Admin+) Full Path Disclosure

2025-04-09 00:00
astra.r3verii

Strategic Overview

Status
Patched in 1.6.1
Affected Version
<= 1.6
CVSS
2.7Low
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-31003
View all Squeeze – Image Optimization & Compression, WEBP Conversion vulnerabilities

At a glance

CVE-2025-31003 is a low-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Squeeze WordPress plugin, affecting versions <= 1.6. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.6.1; sites on affected versions should update now. Disclosed April 2025, reported by astra.r3verii.

Vulnerability Overview

The Squeeze – Image Optimization & Compression, WebP Conversion plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.6. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Squeeze <= 1.6 takes an account at Admin level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Squeeze the fix is 1.6.1: builds <= 1.6 are affected, anything from 1.6.1 onward is not.

Remediation

Update to version 1.6.1, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Squeeze 1.6.1 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C