Image Optimizer by 10web <= 1.0.25 - Directory Traversal to Information Exposure

2023-04-19 00:00
Anonymous

Strategic Overview

Status
Patched in 1.0.26
Affected Version
< 1.0.26
CVSS
4.3Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE pending
View all Image Optimizer by 10web – Image Optimizer and Compression plugin vulnerabilities

At a glance

This record tracks a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Image Optimizer by 10web WordPress plugin, affecting versions < 1.0.26. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 1.0.26; sites on affected versions should update now. Disclosed April 2023.

Vulnerability Overview

The Image Optimizer by 10web plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 1.0.25 via the dir parameter in the get_subdirs AJAX function. This allows authenticated attackers with subscriber-level permissions or above to view the directory structure of arbitrary folders on the server, though it does not reveal or provide access to any files.

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 Image Optimizer by 10web < 1.0.26 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 Image Optimizer by 10web the fix is 1.0.26: builds < 1.0.26 are affected, anything from 1.0.26 onward is not.

Remediation

Update to version 1.0.26, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Image Optimizer by 10web: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Image Optimizer by 10web 1.0.26 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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